I'm trying to deploy a .NET 4.0 project with Visual Studio 2010 using MSDeploy; however when I right-click on the project, what shows up is the legacy context menu for Visual Studio 2008 ('Publish Website', 'Build Website' etc.) in lieu of the VS 2010 context menu ('Publish', 'Build' etc.). I'm running Windows Vista and IIS 7.0.
Ideas, anyone?
Thanks...
It appears this happens when you open a Framework 3.5 solution using Visual Studio 2010
This happens when a website is created as opposed to a web project.
Related
Goal:
I try to open a visual studio project (c#) with CLR code for SQL Server from the Pluralsight course.
Issue:
I get no error messages just warnings below after One-way upgrade on Visual Studio 2017.
Your project is targeting .NET Framework 2.0 or 3.0. If your project
uses assemblies requiring a newer .NET Framework, your project will
fail to build. You can change the .NET Framework version by clicking
Properties on the project menu and then selecting a new version in the
'.NET Framework' dropdown box. (In Visual Basic, this is located on
the Compile tab by clicking the 'Advanced Compiler Options...'
button.)
When I open a solution with single project inside I get message below
The Project Needs to be migrated
or
The Project Needs to be loaded
Tried:
I tried editing csproj files with newer/older version numbers.
I tried different PCs with Visual Studio 2017 and Visual Studio 2015
Idea: Install Visual Studio 2010 as course was released in 2010 BUT I really do not want that.
When I got this issue, I tried reloading the project and when I did, it told me that I did not have an SDK installed and then it offered to install the SDK. Once I had the SDK installed, the project loaded and I was able to work with the project.
http://i.stack.imgur.com/k5fN5.jpg
I can't create a new ASP.NET Web Project via template. Clicking on "OK" crashes VS 2013 or shows the error message "Object reference not set to an instance of an object".
I'm using MS Windows 8.1 + Visual Studio 2013 Premium Update 3.
Extensions I am using:
.NET Reflector Pro
Brace Completer
Visual Power Tools
Web Essentials 2013 for Update 3
Maybe someone knows whats going on? I am running VS 2013 as admin. :(
I tried disabling all Extension, doesn't help.
It's a fresh install from MSDN.
Edit:
I just recognized that the templates show up, when I choose a .NET framework below 4.5:
http://i.imgur.com/rK6AzNR.jpg
EDIT 2:
Okay, reinstalling didn't help. I also uninstalled everything .NET related.
Okay I found the Problem.
in C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\PrivateAssemblies are three assemblies that prevent VS 2013 from showing up the assemblies. See this Question/Answer:
Can't create new MVC5 project or any other ASP .NET projects in Visual Studio 2013
I have several projects that opened just fine in Visual Studio Web Developer 2008 Express Edition, but can't be opened in VS 2008 Professional Edition! These projects are just .NET Framework 3.5 class libraries, and they are on the same machine.
The error is "The project [myproject.csproj] cannot be opened. The project type is not supported by this installation.
Thanks.
Upon inspecting the project file, it seems like the project type have references to ASP.NET MVC 1. Installed MVC 1 solved the problem. Thanks!
I have several wdprojects (web deployment 2008) in vs2008 solutions.
When I installed vs2010 RC none of my wdprojects will open.
What can I do to make it work?
Visual Studio 2010 Web Deployment Projects RTW is available here: Visual Studio 2010 Web Deployment Projects RTW
Update:
As per this SO question, Visual Studio 2012 does not have Web Deployment Projects.
But it's ok: Visual Studio 2012 Web Deployment Projects are Dead – Long Live Publishing Profiles
According to this post on the ASP.NET forum they will actually provide support for it some time after the release of Visual Studio 2010. But I can confirm that it is not supported out of the box in the Visual Studio 2010 RTM.
Note there could also be some conflicts/warnings or errors when migrating.
Something like:
"Unrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive"
Here is an article which explains how to fix that:
http://extremedev.blogspot.com/2011/10/migrating-wdproj-from-vs-2008-to-vs.html
VS 2010 convertor will convert the project as required when you try opening it in VS2010.
I was hoping there would an option somewhere that would just let me open my VS 2008 projects and continue working in .Net 3.5 - while using some of the neat new VS UI enhancements.
Yes, Visual Studio 2010 allows you to target previous versions of the CLR/.NET framework at the project level.
When you open the Visual Studio 2008 project file in Visual Studio 2010 it will convert the project file for you. Once this is done, it will be smart enough to target the proper framework and runtime version for you (.NET 3.5 and CLR 2). If it doesn't, you can change this yourself on the property sheet for the project.