Develop simultaneously with 2 LLBLGenPro versions

Posts   
 
    
Alvaro
User
Posts: 52
Joined: 01-Jun-2004
# Posted on: 02-Jan-2006 14:48:18   

Hello,

Currently we are developing with the October 10th version of LLBLGenPro (it shows as 1.0.2004.2 final, August 5th, 2005).

It just so happens that one of our developers is also giving support and fixing bugs for a customer we installed when we were using version 1.0.2004.1. Now, we don't want to change that customer's LLBLGenPro assemblies version to 1.0.2004.2, they should keep on using 1.0.2004.1. However it is a bit of a pain for that particular developer, as he sometimes needs to compile against version 1.0.2004.2 and sometimes against version 1.0.2004.1, and we have found no easy way to do this, because Visual Studio always wants to reference the current installed version under program files\solutions design cry .

Any comments on this...? It would be much better if there was a simple way for him to compile against a given LLBLGenPro version disappointed .

Thanks for your comments, álvaro.-

Walaa avatar
Walaa
Support Team
Posts: 14946
Joined: 21-Aug-2005
# Posted on: 02-Jan-2006 14:57:16   

I've been through this situation before. I had an older version and I wanted to install a new one and work with both. Here is what I did:

1- Copied the old version from "Program Files\Solutions Design" to a new location 2- Add/Remove programs, and removed the installation of the older version 3- Installed the new version 4- Let my older projects refer to the new location of the old runtimelibraries. 5- New projects refer to the newly installed runtimelibraries 6- Both worked fine 7- I can open both Designers, each from his location and work with it nice and easy.

Good Luck

Alvaro
User
Posts: 52
Joined: 01-Jun-2004
# Posted on: 02-Jan-2006 21:12:47   

So you mean Visual Studio doesn't get it wrong when referencing the runtime libraries? I will certainly give this a shot simple_smile thanx!

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 02-Jan-2006 21:39:48   

VS.NET works fine, as the versions aren't the same (1.0.2004.1 vs. other version). simple_smile As a rule of thumb when working with older versions, copy the runtime libs to a central location and reference them from there, so stored per version.

Frans Bouma | Lead developer LLBLGen Pro
Alvaro
User
Posts: 52
Joined: 01-Jun-2004
# Posted on: 02-Jan-2006 22:14:46   

Well initially we tried to do something like that but it didn't work.

Basically we put LLBLGenPro's runtime libraries under source control, and told VS to reference them from there, hoping to enable a private workspace for all source versions. The idea was that if a certain version of the source code was meant to be built against a certain version of LLBLGenPro, then you could checkout that version of the source code and you would get all the proper versions together.

VS.NET effectively defeats that tactic by searching the registry for every reference on startup, and CHANGING your carefully built project files to reference the newly found versions. So whenever we opened our solution, it found the more recent version of LLBLGenPro under \program files...

Maybe this is different in some way and it will work properly, I'll try simple_smile

Most of the time I hate VS.NET so much...

Walaa avatar
Walaa
Support Team
Posts: 14946
Joined: 21-Aug-2005
# Posted on: 03-Jan-2006 07:11:02   

check the working folder of the RuntimeLibraries in the source safe, and whether you point to this folder in your project references or not, and if the property 'copy local' is true delete all the dlls in the bin folder and rebuild.

Posts: 77
Joined: 05-May-2005
# Posted on: 01-Feb-2008 17:30:27   

On a somewhat related note, I am going to be developing new .NET applications and will want to use the 3.5 version of the framework. Does LLBLGen have a version that supports that? If so, which version?

Also I have an existing application that was coded using framework version 1.1 with LLBLGen version 1.0.2004.2. Does anybody have any experience upgrading a project this old to the 3.0 or 3.5 framework with a newer version of LLBLGen? Any tips and/or horror stories are appreciated. :-)

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 02-Feb-2008 13:33:15   

jlkInChantillyVA wrote:

On a somewhat related note, I am going to be developing new .NET applications and will want to use the 3.5 version of the framework. Does LLBLGen have a version that supports that? If so, which version?

Our .NET 2.0 builds work fine for .net 3.5, which is actually the .NET 2.0 CLR and different compilers and a couple of extra assemblies. The 2.5 designer has vs.net 2008 project templates.

Also I have an existing application that was coded using framework version 1.1 with LLBLGen version 1.0.2004.2. Does anybody have any experience upgrading a project this old to the 3.0 or 3.5 framework with a newer version of LLBLGen? Any tips and/or horror stories are appreciated. :-)

.NET 1.x to .net 2.0 is what's problematic, as there are a couple of breaking changes in this traversion. moving from .net 2.0 to 3.0/3.5 is smooth.

Migrating from 1.0.2004.2 to v2.0 / 2.5 of llblgen pro will give you a set of breaking changes. These are all documented in the manual under migrating your code.

Frans Bouma | Lead developer LLBLGen Pro