I installed Microsoft Visual Studio and during installation i think i somehow ticked the Team Project checkbox. Now i'm unable to create a normal ASP.NET website in any way. I would be very grateful if someone tells how to fix this thing. Also i have uninstalled and installed seven times. But no luck. Thank you.
If I have understood You right. You try to change default templates in IDE for Web developers.
In Visual studio you can easily change the profile of the IDE by going to Tools -> Import Export Settings. This brings up Import Export Windows Wizard. Follow the simple Wizard (which also allows to save you the current settings for future use) and select the new profile setting (based on the kind of project you are working on) and you are ready to work with new profile.
I assume You need to choose "Web development".
Related
I have an ASP.NET C# WebApi project in Visual Studio which I develop for some years now.
Suddenly, the Publish button is missing from the Build menu, so I cannot publish the changes I made.
I already uninstalled and installed again Visual Studio (with different options selected), updated to the last version, reset all settings in Tools > Import and Export Settings and applied General and Web development settings, nothing works.
I tried to install in another computer, and it is there. Tried to export the settings and import in the computer I need to use, and does not work.
Everything apart of this is working.
Do you have any clue what is causing this?
Thanks in advance.
I had the exact same problem. In my case it was self inflicted.
My project file (.csproj) was missing the <ProjectTypeGuids> setting. When I copied one over from another similar project (that had the publish option) the issue was resolved and I could once again Publish from the context menu.
I seem to remember removing the <ProjectTypeGuids> entry to get over another Visual Studio issue that I was experiencing at the time :(
When I run my Web API application I get the following window:
It just stays like that indefinantly, until I hit cancel.
When I do hit cancel, this error message is shown:
I have tried rebooting, and running iisreset /restart but it does not fix it.
Any ideas what I can do to get my debugger working again?
NOTE: My Web API 2 project's Servers setting is set to Local IIS. My service is hosted by IIS and when I am not debugging, it works fine.
A possible fix:
Check the "Enable Just My Code" in Tools->Options->Debug
I just did a reset for all the settings for VS and it worked again.
Tools => Import and Export Settings => Reset All Settings
good luck!
I had this issue for Visual Studio 2017 and like with the previous post I had Debugging option "Enable .NET Framework source stepping" ticked. Un-ticking fixed the issue.
So as I commented before I had this same issue, but I now figured out the cause and have a solution.
I just got a new machine last week (this issue was actually one of the reasons why) and after a while I had the same issues, not being able to debug my projects. Luckily because I was installing all the updates one by one I was able to pin-point when it started happening.
It seems the latest update for the "Microsoft ASP.NET and Web Tools" extension breaks something.
Sadly, uninstalling or reverting the Web Tools extension is not easy: Remove this extension by going to the Windows control panel and modifying your Visual Studio installation. I had to remove Visual Studio completely and reinstall it (repair didn't do the trick).
You can update and install all your extensions as you wish, just make sure that you don't update the Web Tools extension
I tested this on my old machine and it did the trick there as well.
I've also created an Issue on GitHub as I won't be updating the extension until this is fixed, if anybody has additional information please add it to the Issue.
In Visual Studio 2015, go to Tools -> Options -> Debugging and deselect "Enable .NET Framework source stepping". This may relate to an issue with loading symbols, so if you want to keep the ability to debug .NET Framework source, then it may help to search the web for how to clear the symbol cache, or preload it, or set your symbol server, and so on.
In Visual Studio 2017, I just restarted my machine and ran the solution, no other windows opened not even a browser, although visual studio took a long time to open (30+ projects in a solution) the problem did not reoccur.
I had the same issue in VS 2017 and un-checking 'Native code' did the trick. Not sure why it was checked.
In my case I set Debugging ->Symbols -> To "Load Only Specified Modules" to include the symbols for, in my case a devops symbols feed for some internal NuGet packages
Options>Debugging>Symbols>Load Only Specified Modules
By checking the option "Always load symbols where located next to modules" the setting won't mess with the regular/classic debugging in VS for your own code
This way the Symbols are still loading where needed and Visual Studio is not trying to load debugging information for all the IIS .net dlls that were loaded by w3wp
Alternatively it can also be configured to not load symbols for microsoft.*.dll and it will also work.
Didn't see this in the current answers, so thought I'd give my 2 cents in 2022:
What worked for me:
Make sure to check that your IIS application pool hasn't been stopped (and restart it if it is), and then if that's not the case, restart your IIS server.
If you don't where those settings are, open our Internet Information Services (IIS) Manager, Application Pools are in the left-hand column, and restart/start/stop your server is in the right column.
Visual Studio 2012 will not allow me to set multiple startup projects.
I have tried:
Right-click the solution / Set StartUp Projects...
Result: Nothing happens.
View / Property Pages
Result: Popup "Object reference not set to an instance of an object."
I have no add-ins running, and disabled all extensions that can be disabled without uninstalling. Active extensions are
Microsoft Web Developer Tools
NuGet Package Manager
Visual Studio Extensions for Windows Library for JavaScript (1.0.8377.0 AND 1.0.9200.20512
VisualSVN
Is this a known issue? Is there a fix/work-around? Can I specify the startup projects by editing the .sln/.csproj file if the VS2012 UI continues to fail?
I'm pretty sure this has to do with NuGet Package Manager. I did as described here.
Uninstalled NuGet Package Manager in Tools => Extensions and Updates... and restarted Visual Studio 2012/Visual Studio 2013 Preview. Now I can happily configure my solution properties again!
Installed NuGet Package Manager again and the problem reappeared. :(
This is a palliative answer. If there's a definitive answer, please share it! :)
Make sure you vote on this Connect Bug.
Found this post while searching for a related issue I was having. I thought it would be helpful for others to know what I found.
My problem was trying to switch between start up projects, IIS Express would always load the same project. My solution was to edit the project properties >Web> assign a different port number for each project. Now when I select Set as StartUp Project... it actually works
Note** I did not have any issues with NuGet probably because I'm using the released version of 2013
I've searched high and low for the answer to this and can find nothing on it. I have installed VS 2010 pro edition on a virtual machine running MS XP Pro. After connecting to my database, I can see all the tables, stored procedures, and functions just fine in the list. However, when I rick-click on any of them, the options to create new/edit/run any of them are missing.
This is not the first time I've set up VS 2010. I got a new laptop so reinstalled everything. I changed no settings the first time I've set this up, and none this time. I set up the connection to the databases the same way each time, and even looked at my old connection settings while I set up this installation. The old installation had all of the right-click options, but this one does not. I have tried going to Tools -> Import and Export Settings -> Reset all settings and tried General Development Settings, Visual C# Development Settings, and Web Development as the default collection of settings. None of these worked.
I've looked through the settings and found nothing for the right-click menu. It almost seems as if the database connection is open in a "read only" mode, but there doesn't seem to be a setting for that, so I don't think that is the case. If anyone knows of any way to get these options to show up, I would greatly appreciate the input. Thanks in advance.
After I installed Visual Studio 2010 (Ultimate), I accidentally uninstalled the SQL Server Data Tools which were installed together with VS, and after reinstalling them (by repairing the VS installation) the missing context menue options were back again.
Desperate to resolve this, I played around with the connection more. I had originally chosen Microsoft SQL Server as the data source, and .NET Framework Data Provider for OLE DB as the Data Provider. Evidently, the data provider was wrong. After choosing .NET Framework Data Provider for SQL Server, it worked and I could see all of my right-click menu options.
I have VS 2013 Ultimate installation. Along this version I installed SSTD BI. Everything was working perfect until I got the same issue. Right-click on tables or other folders displays only three options: copy, refresh, property. The tricky thing is that it's impossible to uninstall SSTD BI in Control Panel or install SSTD BI on top of previous installation. What helped me is repair installation of VS2013. Start your installation file and chose repair instead of installation. Couple hours and it's back to work.
I downloaded SSTD from here and it fixed my missing context menus
https://msdn.microsoft.com/en-us/mt186501
I have a problem that is described here: TFS: cannot set up new build
I use Visual Studio 2008. Unfortunately, the solution provided there, didn't help.
I tried to remove and add again my TFS server - no help. Also, it's not a problem with security policies or lack of proper right, because I can initiate a new build, with the same user through Visual Studio 2005, also installed on my computer.
In addition my colleagues have no problems at all.
If someone else have experienced similar problem - I will appreciate any help !
If your getting the red cross it is likely that it is a permissions problem. From the 'Team Explorer' window within VS2008, right-click on your project node and select the 'Team Project Settings->Group Membership' menu option. From there trace down the group that your user belongs to.
Next, again right-click on your project node in the 'Team Explorer' window, this time selecting the 'Team Project Settings->Security' option. Within this dialog, find the security settings for your user group. Ensure that the 'Allow' checkbox is set for the 'Start a build' property. Confirm any changes and exit.
I have found that it is best to restart IIS on the TFS server to ensure that the chances are picked up.
Good luck !
Here is what I did. I don't know why the problem is fixed, but it's ok ... for now.
I installed the Microsoft Team Foundation Server 2008 Power Tools and exclusively installed the integration of the tools with Visual Studio. Then I did the following instructions again:
I decided to add my user (just me, not from some domain group) in to the permission menu options ... Then, from security option menu I checked the 'start a build' option at my user and restarted the Visual Studio.
After restarting the Source control menu is a little bit different from what it was before, but at least I can start builds now. Hope It's forever :)
Is the server running TFS 2005 or 2008?
Have you tried running the diagnostics in the BPA Tool?
EDIT:
Team Build had many breaking changes between 2005 and 2008. VS 2008 cannot create new build definitions on a 2005 server. Details: http://blogs.msdn.com/buckh/archive/2007/07/27/team-build-compatibility-between-2005-and-2008.aspx