I have a working solution that started as a visual studio forms web project and solution using 2010 version. I have progressed over the years to VS 2019 and I'm using the latest framework of 4.8.
However, my C# version is 5. I need to upgrade to C# 9 but it is not an option I can find in the project properties window. I would be grateful for some help.
I did try creating a blank solution in VS2019 and importing all the files. I did gain a project window with options I have not seen due to the newer project or solution version. I had 700 or so, errors on build and gave up. Perhaps if I had persevered.
Related
I've been working on a C# MVC application in VS2015 with no problems. Recently I've upgraded to VS2017. I opened the same project in VS2017, but whenever I try to run it, I get the exact same error verbatim as described in
this question VS2017: The debugger is not properly installed. Cannot debug the requested type of code
I've followed every single piece of advice in that thread. I've also performed a repair on my installation - but none of the suggestions worked for me.
It's August now, so I wonder if anything has changed and if there is a solution now.
I have a feeling the problem is probably due to the differences between VS2015 and VS2017 - this was originally something built in VS2015 after all.
I also had issues few months ago when i upgraded VS2015 to VS2017 and one of my big project that i was running on visual studio 2015 stopped working. That project had seveleral class libraries and DLLs added. VS2017 asked me to installed required libraries/ddl one by one, which i did and still didn't work.
So what I did was, Uninstalled the upgraded version of visual studio 2017 and re-installed the complete visual studio 2017 from MSDN website (selecting the default selection of features). And then i loaded my Project in VS2017 fresh copy and it worked.
I suggest you to try the same
How do I convert/downgrade a SSIS package (.dtsx file) that I created in VS 2015 to work with VS 2010? Is there a way I can force this action by changing the .sln settings in notepad? or maybe another work around. I have spent hours on creating packages in VS 2015 and the client is not able to upgrade to 2015 anymore. Any help/guidance is appreciated.
Update: Tried changing the connector to 10.1 - came back with this error:
Trying to make it work on version 2010 shown below:
Post making version change from 8 to 6:
In Visual Studio 2015, open your SSIS project (MyProject.dtproj). You can then go into the Properties Menu and within those menus there, you can specify the version of SQL Server this project should target (2012/2014/2016).
Now that Visual Studio 2015 RC is out, has anyone installed it and opened Visual Studio 2013 projects/solutions?
Does it ask the files to be changed?
If yes, are the changes it makes backward compatible?
Take a look at the Porting, Migrating, and Upgrading Visual Studio Projects article for Visual Studio 2015. All of the various caveats are described there.
Not all types of project are supported. I tried the following 4 project types:
Vb.net Class project, OK.
Vb.net Web Services project, OK.
Cordova JS project, not OK, need to migrate manually, by moving the sources from root directory to the www directory and install all API again.
C#.net winform project, OK.
Yes, though you sometimes will have to change the version (single number) in .sln file, no other differences found yet.
We resolved this by typically excluding this file from check in and only check it in when there really was a change (added project, ...) - and then to fix the version before checking in. (Different developer machines with different versions of VS.)
See question Visual Studio 2015 solutions backwards compatibility with Visual Studio 2013 and answer https://stackoverflow.com/a/31540590/586754.
(Assuming you are having basic projects that are supported by both versions, like C# and .net framework that is supported by lower version VS.)
I create an ASP.NET MVC 3 project and a unit test project using xUnit.net.
new project http://img841.imageshack.us/img841/38/newprojectsnt.png
But I got an error like this, and the unit test project is not created.
error http://img15.imageshack.us/img15/4725/errordp.png
Does anyone know how to fix it? I'm using Visual Studio 2010 Professional SP1, on Windows 8 Release Preview.
Thanks.
I had the same problem while using version 1.9.1 (Jul 4 2012 release). I uninstalled it and installed the version 1.9 (Jul 4 2012 release)and now it is working fine. I'm using Visual Studio 2010 Ultimate SP1 and Windows 7 Ultimate with SP1.
Sorry about this bug. We're planning to remove template support from 2.0 anyway, so this bug is going to go away.
Moving forward, we recommend people just create class libraries, and bring in xunit.dll via NuGet.
I am going to install Visual Studio. I want to know if the latest version of Visual Studio 2010 is backward compatible with previous versions like VS 2005 and 2008. Or is the code functionality and deploy-ability more dependent on the .NET framework version.
I am trying to use a code which will be built into dll. I am not sure in which version of VS the code was written(most probably VS 2005).
Thanks...
I would suggest to go with the latest Version.
VS 2010 can target multiple frameworks.
http://msdn.microsoft.com/en-us/library/bb398197.aspx
So the dll should know with which framework it was compiled...
I have never found any issues with Visual Studio 2010 and previous versions' code. It also does feature significantly improved Intellisense and [IMHO] faster building.
they are all backward compatible
2005 and above allow you to target the framework you want when creating
the project
if the project is older
than the VS, it will prompt you with
a migration wizard upon opening
it(this is a one time only step.
Couple of things to note that i've found with 2010 which have caused us a couple of issues:
1) NHibernate (Castle Proxy) doesn't work with .net framework 4 (Currently)
2) Test Projects are always created aimed at .net framework 4, and you cannot target a lower version of the framework.
Otherwise not many problems, its also nice that the database addition of Visual Studio 2010 has intellisense on your tables/views, as well as many other changes
Always go with the latest, now 2010