VB .net 2003 to VS2010 - visual-studio-2010

I have applications that have been created by a third party. These apps were done by using Visual Basic .NET 2003 with MS .NET Framework 1.1. Now I'm in the need to be able to modify these apps, but it seems that at the moment there is only one possible software to purchase and that is the Visual Studio 2010.
Is it even remotely possible to use this newer version with these old creations, or do I have to rewrite the entire code?
If it is possible, I reckon if I make modifications with VS2010, it is impossible to do anything with VB .NET 2003 afterwards?

You can upgrade the projects to VS 2010 and .Net 2.0 or 4.0 and work on them there.
It will not be easy to go back again.

Related

IDE / language for Okuma machine tool control development

I'm trying to set up some new developers to make apps for the Okuma control using the Okuma API and SDK. What environment should they use? I tried installing Visual Studio Express 2012 but it keeps giving an error looking for files during install. Also, what language should they use so they can work with the Okuma API?
The Okuma API is written using .NET 4.0 so you really have several options.
Normally I'd say Visual Studio express 2012 for desktop is best but I've seen problems putting it on Windows XP.
If you're using windows XP and aren't ready to invest in a full version of Visual Studio yet, I'd recommend Visual C# Express 2010. If you're more familiar with VB and don't want to switch, do the VB express verison.
All these (and the professional version) are available from
www.microsoft.com/visualstudio/eng#downloads
VS 2019 community edition is currently working fine for me doing this. I just have to choose which .net framework in the project settings. That was not listed in the prior answer in case anyone comes across this in the future.

What Visual Studio for .NET 1.0 web development?

I have a old web application developed in .NET 1.0. How can I do some minor changes in it? What Visual Studio do I need and how do I obtain it? Or can I develop in some other tool?
Thanks in advance!
It was called VisualStudio.NET, followed by Visual Studio 2003 (also known as version 7.1).
I don't think this is available anymore, unless you have a pro MSDN subscription or above.
Visual Studio 2005/2008/2010 cannot be used for this, nor can mono-develop, but you might be able to use the version of SharpDevelop that supports 1.1.
You'd need Visual Studio 2002, it targeted .NET 1.0. That edition didn't last long, Visual Studio 2003 and .NET 1.1 quickly followed. Your project should have good odds opening and running properly on that edition. Odds get lower once you move to VS 2005/8 and .NET 2.0+
If you don't have VS2002 then you can obtain a license through an MSDN Library subscription. An auction site like Ebay is a cheaper alternative.
It was originally called Visual Studio.NET but later on also got referred to as Visual Studio 2002.
I looked it up and apparently you can still download it if you have an MSDN subscription.
You can use VS 2005, VS 2003, or VS 2002. I think the 2002 edition was called VS.NET.
From http://weblogs.asp.net/scottgu/archive/2007/06/20/vs-2008-multi-targeting-support.aspx
What about .NET 1.0 and 1.1?
Unfortunately the VS 2008 multi-targeting support only works with .NET 2.0, .NET 3.0 and .NET 3.5 - and not against older versions of the framework. The reason for this is that there were significant CLR engine changes between .NET 1.x and 2.x that make debugging very difficult to support. In the end the costing of the work to support that was so large and impacted so many parts of Visual Studio that we weren't able to add 1.1 support in this release.
VS 2008 does run side-by-side, though, with VS 2005, VS 2003, and VS 2002. So it is definitely possible to continue targeting .NET 1.1 projects using VS 2003 on the same machine as VS 2008.
Take a back up of your project.
Try to down load visual studio express 2008 version and open the project. you will have an option to convert. Once converted download the latest visual studio express and then convert into the latest version.
BTW Visual stuido express is FREE
Note:
Some of the methods may not be supported or droped. you need to recode them or replace them.

If I have Both Visual Studio 2008 and 2010, do have I have to keep both

I recently downloaded VS 2010 trial, the new version is more easy to use.
I have VS 2008 installed, If i decide to use VS 2010 in the future, do I still have to keep VS 2008? Is there any compatibility issue with it?
You would need to keep VS2008 installed if you target Windows CE (via Compact Framework, native smart device projects, etc.)
http://msdn.microsoft.com/en-us/library/sa69he4t.aspx
Also if you want to write native applications that run on versions of Windows before XP SP3 and Server 2003 SP2, this is no longer possible with VC++ 2010. The same applies to managed code written for the .NET Framework 4.0, but you can still use Framework 3.5 with VS2010 for projects with managed code only.
And Intellisense for C++/CLI code is gone (MS promises to remedy that in the future, whether a service pack or the next version I cannot say).
If you open a VS 2008 solution or a project in VS 2010 it will be converted to VS 2010 and you will not be able to open it in VS 2008.
If that is not a problem then you don´t have to keep VS 2008, unless you are using a addin or some other third party application with VS 2008 that is not compatible with VS 2010.
Edit:
Look at Ben Voigt´s answer for information for which version have support for different platforms.
VS2010 allows you to specify the target framework that you'd like to develop on. There should be no reason to keep VS2008 installed unless you've become accustom to some handy plugins :)

Visual studio 2008/2010 dilemma

We have a project which is being developed by a 3rd party. They are using LINQ and .NET 3.5 with Visual Studio 2008. We are currently at 2005 with .NET 2. Once they have delivered the code to us, we are unsure as to whether we will be able to compile/build their code using our current Visual Studio toolkit. I know we can download .NET 3.5, but unsure as to whether we will have problems with Visual Studio.
So we are considering to upgrade. But since Visual Studio 2010 is soon to be released do we wait for that or upgrade to 2008?
Here's a plan:
Upgrade to RC now for non-critical
items. Gain familiarity with it.
Test your 3rd party app in RC to
identify any issues.
Add an addendum to your contract
with the 3rd party that they will
need to deliver the app in .NET 4.0 RTM,
compatible with VS2010 RTM, i.e. get
them to upgrade too!
Upgrade to 2010. We talk of a month here until you get your hands off. AND it being in RC status (so you can actually test now that it compiles etc- no major changes coming). note that I don say go .NET 4.0 NOW - just use VS 2010. No sense in moving to 2008 at this point in time at all.
With the release being so close I would wait for the upgrade and use the release candidate until then.
Seems to be a no brainer. Unless you have immediate operational needs, you can wait for VS2010 and/or better yet, install and use the release candidate (in a non-critical workstation / role) and get acquainted with the new stuff.

Is it possible to use C# 4.0 with Visual Studio 2008?

I'm pretty aware that Visual Studio 2010 works with C# 4.0. But now I was wandering if I'm able to test C# 4.0 features with Visual Studio 2008.
I did that one time, using C# 3.0 with Visual Studio 2005 hacking the app.config file.
Did anyone have any success using C# 4.0 in VS2008?
I've installed Net Framework 4.0 beta, rebooted, created a new WPF application, chosen Application properties, but the Target Framework can be set only to Net Framework 3.5.
No. You can't use .NET 4.0 with VS2008, and you can't use the C# 4.0 features either - it's exactly the same situation as trying to make VS2005 cope with C# 3.0. The editor, Intellisense etc just don't know about the new features.
One important aspect is that even though it looks like Visual Studio is just using the external csc.exe compiler, it isn't - there's another "in-process" one. That in-process compiler is tied to the version of Visual Studio it comes with, so it only knows about the language features which were available at the time.
The 3.0 and 3.5 .NET libraries were just add-ons to 2.0. So it ws possible to test work done in VS 2008 using VS 2005 if you didn't use any 3.0 or 3.5 features.
My understanding is that the 4.0 is entirely new libraries, so I doubt you will be able to load or use them in VS 2008/2005.

Resources