Convert Project between Express <-> Professional versions of VS

[IanS]

I use VS2005 Pro on one computer and Express on a couple of others.

I've never had any problem moving my projects from one to the other (Just simple windows apps - Not using any 'Pro' features)

But I've recently read on blogs and other forums people asking the question about how to convert from express to pro and/or back again. and the answers are quite long and complex.

They kind of suggest that the projects are simply not compatible with each other and require the making/copying of templates, editing of headers etc.

What are they talking about ? I've never had to do any of that. Have I just been lucky in that my projects just happen to be compatible ?

Anyone ever have problems moving a project between express and pro versions of VS ?

[Hack]

No...none.

Can you post a couple of the links you mention...I'd like to read those articles.

[IanS]

Here's one.

http://jamesewelch.wordpress.com/200...-2005-express/

[techgnome]

I know there are problems between VERSIONs (2005-2007-2010) but there aren't differences between the EDITIONS... (can't get to the link, so I could see what that posting is about)... something certainly isn't right.

-tg

[JuggaloBrotha]

The Express Editions will open what they can from a solution file. So if you have your project and a setup & deployment project set up in the same solution then go and open it in VB Express, the Express IDE will open the project (because it knows how) but will not open the setup & deployment project (because it doesn't know how to) but it doesn't corrupt or remove anything either, so when the project's moved back to the computer with the full edition, everything just works.

I haven't read that article you posted, all I've done is explained what I, personally, have done many times before. I've done it between VS 2005 Pro and VB2005 Express, as well as between VS 2008 Pro and VB2008 Express, I have not done it with VS 2010 at all yet so I can't speak for it, but I don't see why MS would want to change it because it'll just cause more headaches than it's worth.

Anyways the point here is, regardless what articles you're finding, what you're currently doing is fine and wont cause any problems for ya.

[IanS]

....... the Express IDE will open the project (because it knows how) but will not open the setup & deployment project (because it doesn't know how to)......

Thanks for that - I never noticed that - are you saying that that's one of the limitations in the express edition - the ability to create/manage deployment projects.

I guess lots of people only have express - How do they deploy their apps ? Or have I misunderstood something.

[NeedSomeAnswers]

I guess lots of people only have express - How do they deploy their apps ? Or have I misunderstood something.

Yes In Express editions you can't create deployment packages, although i think you can do ClickOnce deployment, although i haven't really used it.

[dilettante]

I guess lots of people only have express - How do they deploy their apps ? Or have I misunderstood something.

You'd be amazed how many people try to do it hackishly and seldom succeed.

In Express you have two options: create such simple applications you can use XCopy deployment or use ClickOnce.


Remember, most of the market for Express are people who will never have a second person run their programs.

[JuggaloBrotha]

Thanks for that - I never noticed that - are you saying that that's one of the limitations in the express edition - the ability to create/manage deployment projects.

I guess lots of people only have express - How do they deploy their apps ? Or have I misunderstood something.

You'd be amazed how many people try to do it hackishly and seldom succeed.

In Express you have two options: create such simple applications you can use XCopy deployment or use ClickOnce.


Remember, most of the market for Express are people who will never have a second person run their programs.

Plus to add on, even though you developed the app in VS that doesn't mean you have to use VS to create a deployment package, there are programs out there like Inno, for example, that'll create installer packages for your apps.

[IanS]

. . . there are programs out there like Inno . . , for example, that'll create installer packages for your apps. . .

Yes, Inno is what I use for deploying my older VB6 applications. Using Inno it's been very easy to keep those old apps with all their dependencies installing cleanly on Vista and Win7

My latest project though is targeted at .net 2.0 and not using any 3rd party controls/classes etc.

Are you saying that as long as the user has FrameWork2 then I don't actually need to deploy anything else - I can simply get Inno to create the program files folder and startup shortcuts etc and put my executable (exe file) into the program folder and that's it ?

[JuggaloBrotha]

Yes, Inno is what I use for deploying my older VB6 applications. Using Inno it's been very easy to keep those old apps with all their dependencies installing cleanly on Vista and Win7

My latest project though is targeted at .net 2.0 and not using any 3rd party controls/classes etc.

Are you saying that as long as the user has FrameWork2 then I don't actually need to deploy anything else - I can simply get Inno to create the program files folder and startup shortcuts etc and put my executable (exe file) into the program folder and that's it ?

Your app does have a dependency (the .Net Framework) so Inno should check for that dependency during install. If the end user(s) already have .Net installed then it wont matter, but what if someone wants to install your app and they don't have that version of .Net installed? That's the main purpose of installers, other than putting all of your app's files in the correct place(s) and creating the shortcuts automatically.