*Experts* Merrion Posted February 25, 2003 *Experts* Posted February 25, 2003 So - I upgraded to VS2003 and recompiled the prin chserver.net component no problem. Now anybody opening the component from VS.Net 2002 gets a stupid "The implementation has changed" error and if they try to open the source code they get "This code was created with a newer version of Visual Studio" so - in order to run my code they will have to upgrade as well???? Note that the code hasn't actually changed - I just opened it up in VS.Nret 2003 and recompiled it! Any thoughts? Quote Printer Monitor for .NET? - see Merrion Computing Ltd for details
*Experts* Merrion Posted February 25, 2003 Author *Experts* Posted February 25, 2003 Checked through the help and it seems that the solution ffile is converted to VS.Net 2003 and this is one-way. So this effectively means we will need to maintain seperate copies of the solution for VS.Net 2002 and 2003 (or only use the older version?) Quote Printer Monitor for .NET? - see Merrion Computing Ltd for details
Moderators Robby Posted February 25, 2003 Moderators Posted February 25, 2003 So other than the Solution, all else remains the same? Quote Visit...Bassic Software
*Gurus* divil Posted February 25, 2003 *Gurus* Posted February 25, 2003 What about the project file? If all was the same except the Solution file itself that would be ok by me. Quote MVP, Visual Developer - .NET Now you see why evil will always triumph - because good is dumb. My free .NET Windows Forms Controls and Articles
Moderators Robby Posted February 25, 2003 Moderators Posted February 25, 2003 Yeah and all you need is to maintain one file Quote Visit...Bassic Software
*Experts* Merrion Posted February 25, 2003 Author *Experts* Posted February 25, 2003 Nah - the dll compiled in VS.Net 2003 wont work in VS.Net 2002 - it complains about not being able to resolve something or other. Anyway - two seperate machines with two different setups for the moment until I work out what is going on... Quote Printer Monitor for .NET? - see Merrion Computing Ltd for details
*Gurus* divil Posted February 25, 2003 *Gurus* Posted February 25, 2003 Well the DLL you compiled using VS.NET 2003 uses a newer version of the framework, so that isn't surprising. I have it on good authority that VS.NET 2003 can compile solutions to be version-compatible with VS.NET 2002. In the build configuration, you can select which .NET platform to build for. Hopefully that'll solve your problem. You can also add the following line to your app.config. <supportedRuntime version="v1.0.3705"/> Quote MVP, Visual Developer - .NET Now you see why evil will always triumph - because good is dumb. My free .NET Windows Forms Controls and Articles
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.