I'm working with VWD2010 and as stated in the topic title I have zero intellisense usability for my project.
I installed VWD2010 fresh a few months ago to start and noticed that intellisense wasn't working. For the last three months I was working with VS2010 trial and intellisense was working fine. The trial version expired, so now I am back to VWD2010.
Intellisense seems to work for NEW projects, so I created a new project and transferred all my files from the VS2010 project. Intellisense was working fine for a couple of days, but this morning I am back with it not working...
I have checked the following:
Intellisense works for new projects;
Intellisense is switched on in the editor settings;
I have reinstalled VWD2010 several times before without it making the blindest bit of difference;
I have reset settings both via the Options menu and via the command line, again without it making the slightest bit of difference.
Intellisense was definitely working for this project last Thursday evening when I last switched off my computer.
I have googled this issue several times and can't find the slightest bit of info on how intellisense is actually supposed to work. Advice generally resumes to "reinstall VWD" or "reset your settings"... Any help would be greatly appreciated.
Here is a distillation of some solutions that have worked for other users from the MSDN forum thread IntelliSense stopped working:
In Visual Studio, Go to Tools > Import and Export Settings,
and then select Reset all settings.
After closing Visual Studio, move the .suo file to a temporary
folder, and then reopen Visual Studio.
Check that Build Action property of your source files are set to
Compile rather than Content. Setting a file to Content detaches the source file from the rest of the project, disabling IntelliSense.
If you have a web project, exclude the WebConfig from the project and
rebuild the project. Then include the WebConfig.file again.
If you’re using C++, close Visual Studio, and then delete the .ncb
file. The ncb file contains IntelliSense information for C++. Deleting it resets IntelliSense, but it may take a while to rebuild in the background.
Finally, from the post Visual Studio & XAML – IntelliSense Not Working:
If you're using XAML, adding ;assembly= to the end of the custom CLR namespace fixes the issue.
Related
So I right click on the solution > add > new project > find azure function > choose template > create that
And then nothing happens. If I swap to folder view, I see a new folder made for the function, but its an empty folder.
Weirdest thing is, this was working perfectly fine and a moment later, it became how it is right now. I've not updated vs in between, I've not restarted in between. It was literally closed vs, opened again, and then vs broke.
Older solutions that has functions in them, tried creating a new one, doesn't work same story. Made new solutions and start it off with creating a function, didn't work as well. Reinstalled vs, also did not help, still the same issue. Any ideas how I broke vs?
Also, this works from powershell, I can create functions from there and then go back to vs to add an existing project. However the functions I've build using this method had runtime errors (I think) when I publish them into azure. Regardless, I really would like to be able to create functions normally in vs.
As we can see from the comment section of the question, the solution was:
Go into Tools -> Get Tools and Features
download the .Net desktop development
As Maybemonday described in his/her comment, functions can be created afterwards.
You can solve the issues by installing the right tools.
When setting up the VS 2022 -OR- by navigating to Tools -> Get Tools and Features, install the following workloads:
.Net Desktop Development
Azure development
You can also observe the icon changes from a "Project" type to "Azure Function App" type.
I'm not sure why, but once I renamed C:\Program Files (x86)\dotnet to C:\Program Files (x86)\dotnet.delete, it started working. I think the x86 dotnet binary was earlier in the path and was causing issues.
This is related to work I am doing for school, but my issue appears to be a problem with a setting in the IDE not any of the code I am writing for my class.I tried searching for a related post, but nothing seemed close. If someone does find something I apologize for the duplication in advance and appreciate any guidance.
I have written some files using the Visual Studio IDE and they save out as .sln files which when I run them they go without an issue. Up until a couple of days ago files I had written before I could access the underlying .vb file and run without a problem.
However I must have mistakenly made some sort of settings change that I cannot figure out how to back out of. Now both the older programs and new ones the .sln files will run, but the .vb files will not. There is no error message, but any options in the IDE to run the code directly from the .vb file are greyed out. I even tried running vbc.exe from the developer command line on the files to see if there was some sort of language issue, but all of the .exe's built correctly and ran as expected. So I really have no idea what could be wrong at this point.
Has anyone ever heard of such an issue? Is there any setting related to Visual Studio that can account for this behavior? Thanks in advance for your patience and assistance.
Recently Edit and Continue with VB.net has been kinda flaky.
In one project in particular. It was working as expected the last time I touched this project.
Recently when I pause the project while the winform message pump is running, I get a message saying no code is running. When I go back to my class file (in the same project, not external) I cannot make any changes - typing does nothing in the editor.
I have another class which is part of this solution, it has no entry point but I thought I would remind VS which was the startup project. This made edit and continue seem to work. I could make changes in the code, but when I continued the old version of the code was what was actually running. It's as if I am in an external class.
I just noticed something else, when you first start the project, edit and continue seems to work fine. After you continue, if you break the code again, it stops working.
I never had edit and continue problems at all with VS2012.
VS was hanging and crashing a lot yesterday so I rebooted my computer. That did not help this problem. I also installed SP1 and that did not fix anything.
I tried compiling to X86 and Any CPU.
Is there a setting I am missing? How can I get this working?
Thanks,
Brad
I tried a few more things based on some suggestion in other forums.
I repaired VS, I reinstalled VS, I tried to restore my default settings. None worked. I tried a simple project to duplicate the issue that I could share to get feedback. I could not get it to not work.
So assuming then the problem was with my project and not VS I made a new project and brought over my forms, modules and classes from project with the problem. I added my references and... edit and continue now works! The only things I changed from the default project were: Target CPU: x86, and Target Framework: .Net Framework 4
I still do not know if there was some corruption or it was a bad setting. This project was originally ported from VB6 many years ago and has been through a few VS upgrades as well.
I have a question about importing a National Instruments (NI) library to my Visual Studio 2012 project. (Using Visual Basic .NET, Windows 7 and Visual Studio 2012)
I currently test the FindReources(NI-VISA) example project to apply some of the functions to my project.
The sample project was working fine, and it was returnning resource data corrent.
However, when I tried to apply Find Resource function to "My project" an error message kept appearing such as "ResourceManager is not declared. It may be inaccessible due to its protection level"
What I did was...
First, I added a reference to my project
Second, I imported "Imports NationalInstruments.VisaNS" to my Visual Basic file
However, the error keep appearing, so I can't use function.
And, when I restart Visual Studio and check the Object Browser, there is a NI-VISA reference and the error is gone.
However, when I run the project, NI.VisaNS library just disappear...
I am not really sure why this happens, because the sample project from NI is working without any trouble.
Is there a missing step to import and use the NI library?
I just found a solution.
The functions which I wanted to use was only working for .NET 4.5. However, my system was using .NET 4.0.
After I switched to .NET 4.5 for my project, it worked fine.
Try to find that file/resource in Solution Explorer. It should be there somewhere in the tree. If it has a blank icon next to it, that means that the file is not included in the project. Click the right mouse button over the file and add it.
I am using Visual Studio Ultimate. I have made a fairly long program which worked fine.
One day I find that the debug button was disabled and both the build and rebuild buttons do not work. I have tried opening the same project files in Visual Basic Express 2010 but still, the sane problem.
I don't really want to have to reinstall but I'm not even sure that that will fix the problem. Thanks in advance.
Is there a startup project? One project in the Solution Explorer should be in bold. Right-click the executable project and select "Set as StartUp Project". Additionally, open the Project Properties, Application tab, and ensure Application type is either "Windows Forms Applications" or "Console Application".
Did you try to reset the setting of your Visual Studio Ultimate?
Type: (In your visual studio command prompt)
devenv /resetsettings
Buttons disabled for just that program, or all programs?
I vaguely remember having a similar problem many years ago. Re-creating the project and solution files fixed it, I think (ie. create a new solution/project and import all the .vb files).
Another thing to check would be whether the compiled files have become read-only. Maybe VB.NET can't delete the old .EXEs
You need to build a test application. I think thats more difficult then making the application itself. In my personal opinion, your better off building the whole software in a notepad.
http://msdn.microsoft.com/en-us/library/ms182532.aspx