I have searched multiple times about this issue and saw thousands of posts here but unfortunately I am still have trouble with the Xamarin Forms Hot Reload while using it on VS.
Any help please??
I have tried every solution but with no success and here are my selections as in the image attached. I have tried also both Changes only & Full Page options but nothing is working. Additionally, I have rebuild my solution many times and my emulator but nothing is functioning. Here are my Hot-reload options.
First of all, update all of your nuget package project to the latest, then close your VS, then delete the 'bin' and 'obj' folders, rebuild and run your project, if it worked as normal.
I've been trying to use Ink for my Unity Project.
https://assetstore.unity.com/packages/tools/integration/ink-unity-integration-60055
After installation through the Package Manager, everything on Unity seems to work fine (Ink files can be created, they get compiled to JSON, the Ink Player tab works, etc etc) - with one exception:
I can't get VisualStudio to find the Ink namespace. I've tried restarting it and Unity. It worked fine for other packages like the new Unity Input system and TextMeshPro.
What can I do to fix this?
Edit: Regenerating project files with all checkboxes checked doesn't seem to work either.
Edit 2: If I open a C# script from Ink itself (Asset/Ink/), then VS seems to recognize Ink.Runtime. Its only in my own scripts (which are also in Asset/) that don't have the namespace:
In this case, I managed to fix it by deleting the ".vs" folder inside the project folder.
So I am wondering how come my IDE1100 is not working. I went to the only question related to this and it was about xamarin, Other Answer, I am not working with xamarin at all. I clicked on the error for more help it said I don't have F1 button workign but it was working then the issues said I didn't have the RazorAssembly.cs or Assembly.cs files were missing. Okay so I did what they told me to do n the link above but unloading and reloading that also did nothing for me. I then ran clean build again then ran a code analysis on the solution and I got all these weird code naming violations and I did not have the originally. It all started from trying to create a new migration because I was changing variable names. I figured well I don't need the database only one person in it and then bam just like that the issue reappeared. I have no clue of what I done to actually create this error. I don't want to restart the whole project again. I am using VS 2022 with MVC project.
So it turns out that it was me that messed up but it would not show my errors at all when I tried to build.
so I clicked on where my mouse is at in the picture and just clicked on the plus sign. It was initially build + intelisense but when I clicked build only it actually showed me an error that was easy to fix. I had to change the view names because I changed them. usually it would show me this error even in build + intelisense this never happened before like wth and you see the name stuff is gone too this is baffeling is this actually normal with vs 2022.
Just about a few hours ago I got here:
InitializeComponent(); and label_link both are properties that either come from XAML behind or init this.
Intellisense shows them as non existing.
Builds however are successful. This issue just appeared out of the blue.
I tried:
Restarting VS
Restarting MAC
cleared BIN and OBJ folder
Cleaned and rebuilded
Unloaded and reloaded everything
deleted .VS (hidden folder)
Other solutions are working fine, it is only this specific problem.
However, this exists in every class of my project now.
Since this is VS for MAC there is no way to reinstall this.
Can anyone help me out here?
So after trying out everything over and over again,
i retraced my steps to what I did prior which was installing
mobile.buildtools and try and set up the sercrets.json file. I removed both cleaned and resetted everything again and finally intellisense was working again and there are no more red lines underneath my code.
I am opening files from a server ASP.net and the VB codebehind files, and my visual studio is not working correctly, Intellisense is dead and if i right click the "Go to defenition" option is disabled. These files are not part of a solution.
This is strange though because it was working properly yesterday. If I create a new project the intellisense works great, yet opening this single file it fails.
I have tried to re enable intellisense by resetting visual studio, I tried editing the text editor settings so that Auto list members and Parameter information are both checked. I even tried installing ReSharper and nothing worked. I have rebooted twice and even tried copying the file to a local drive to work on yet nothing.
Does anyone know why this is happening and what I could do to solve the problem? Im working on a rather complex problem and intellisense would make it a lot easier.
I managed to fix this problem which manifested itself after my ReSharper trial expired.
Steps to fix are:
Tools/Import and Export Settings
Reset all settings
Back up your config
Select your environment settings and finish
Intellisense started working again straight away.
For me simply hitting Ctrl+Alt+Space to re-enable Autocompletion fixed it.
I had the same problem. It only affected one of my solutions. Others seemed fine.
To correct it I deleted the solution's user options file (.suo).
When I opened the solution again, intellisense was working.
For the benefit of searchers, Nicks suggestion is good, but if you don't want to reset all your settings, you could follow the recommendation in this post.
It states - "go to "Tools | Options | Text Editor | C# | General and check the "Auto list members" and "Parameter information" checkboxes"
I should first note that upgrading my RAM from 4 to 16GB seems to have made this issue go away.
Here's the steps I go through:
If only one file/window appears to be affected, close/reopen that file. If that doesn't work, try below.
In Visual Studio:
Click Tools->Options->Text Editor->All Languages->General
Uncheck "Auto list members"
Uncheck "Parameter information"
Check "Auto list members" (yes, the one you just unchecked)
Check "Parameter information" (again, the one you just unchecked)
Click OK
If this doesn't work, here's a few more steps to try:
Close all VS documents and reopen
If still not working, close/reopen solution
If still not working, restart VS.
For C++ projects:
MSDN has a few things to try: MSDN suggestions
The corrupt .ncb file seems a likely culprit.
From MSDN:
Close the solution.
Delete the .ncb file.
Reopen the solution. (This creates a new .ncb file.)
Sometimes, it could be because of different extension style that you are using for the files.
In my case Intellisense is working in all the files except for a file in a different project of the same solution.
When I have changed the extension of the file to cxx from cpp,it started working.
The includes and other files in the solution are of extension .cxx or .txx.
Thank you
Save your solution. Closing the VS2010 instance for this solution and re-oprning worked for me.
Here I assume that Intellisense was working OK but stopped for some unknown reason without changing any default settings.
Prabhdeep
After uninstalling ReSharper, the squigglies that show up underneath a syntax error stopped showing up in the code editor.
This blog post helped me fix the issue.
Try this:
Close any open instances of visual studio, delete the folder 10.0 inside `C:\Users[username]\AppData\Roaming\Microsoft\VisualStudio\' and restart the visual studio. Issue will be fixed.
In my case, none of the above worked (although I discovered that sometimes the *.suo file is the trouble maker - in those cases deleting it helps).
I fixed it successfully the following way: Let's assume your solution has the name MySolution. Do the following:
Reset the settings (as described here). Close Visual Studio 2012.
Locate the file MySolution.sln.DotSettings (it is in the same folder as your MySolution.sln file)
Rename or delete it (for example rename it to XMySolution.sln.DotSettingsX so VS won't read it)
Open your solution by double-clicking on the MySolution.sln file
And afterwards Intellisense was working again just fine. I assume the file MySolution.sln.DotSettings got corrupted.
Note: The file MySolution.sln.DotSettings was created and checked in to TFS by a team colleague who had installed ReSharper. The issue occurred on a different PC without ReSharper where the same project was opened.
For me, this was related to an incorrect xaml file build action in an Azure WorkerRole project (bizarre, though it may seem!). Please see my entry in this post if you want to know more:
C# VS2010 Entering break mode failed
The fix for the error in the above thread also resulted in the intellisense starting to work again.
I fixed this problem by removing Sybase Power Designer VS extension.
You can try to disable other extensions.
Exactly the same issue, though would appear only on certain projects (even within a single solution).
Removing the *.*proj.user file (e.g. *.csproj.user) for the projects in question properly reset the missing features ("Go To Definition", "Organize Usings", Intellisense on certain types, etc).
In our case, I suspect this happens sometimes when we switch branches with an SCM that uses a single working directory (like git). If setup properly, it wouldn't track *.user* files but that means that if there are incompatible changes in it across different branches, you need to regenerate it.
So of course the "sometimes" would depend on the current branch and the next branch.
Unfortunately I don't see a very good solution if that's the case. Sometimes you really want to keep the user settings across branches if they're compatible, sometimes you want to regenerate them unconditionally. Ideally, you might even want to only change parts of them when switching, while keeping other parts.
If you never need to keep them and are fine with regenerating them every time, then you can configure your SCM to always remove these files while switching branches (e.g. using hooks for git). This is a pretty naive solution however, doing it more universally correctly would require a smarter system (aware of the semantics behind the .user files and capable of capturing/prompting user intent when needed).
save, close and reopen the source file you are working on. This works every time for me.
Try to add the statement:
<%# Page Language="vb" AutoEventWireup="false" CodeBehind="Default.aspx.vb" Inherits="IP_Updater.Default" %>
...at beginning of your page. The above example is applied for page Default.aspx written in VB.NET.
This is the problem related to Microsoft MSDN , your MSDN might be getting some problem. The solutions to this is uninstall MSDN and then re-install . before going for this make sure that you system is free from virus attack.
Hope that after doing , the Microsoft Intellisense will start running