Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > LLBLGen Pro Runtime Framework> Multiple versions
 

Pages: 1
LLBLGen Pro Runtime Framework
Multiple versions
Page:1/1 

  Print all messages in this thread  
Poster Message
billb
User



Location:

Joined on:
09-Jul-2004 21:57:41
Posted:
50 posts
# Posted on: 24-May-2005 20:34:51.  
This seems like an FAQ type item, but I didn't find anything related to my question.

Please send me to the proper page, if I missed it.

I'm starting a new project w/ LLBLGen but I also have two other projects that I've been using LLBLGen with quite happily for over a year now. I still have to maintain these projects and I'm not prepared to fully test them with the new version just yet, but moving forward, I would like to use the new version.

So my question is, can I run the two versions side by side? I know .NET is supposed to allow this without problems, but unfortunately, I have run into problems in the past with other products, so I thought I'd ask.

Thanks.
  Top
billb
User



Location:

Joined on:
09-Jul-2004 21:57:41
Posted:
50 posts
# Posted on: 24-May-2005 21:36:29.  
I answered my own question by trying to install the newer version. It isn't allowed. Dissapointed

billb wrote:
This seems like an FAQ type item, but I didn't find anything related to my question.

Please send me to the proper page, if I missed it.

I'm starting a new project w/ LLBLGen but I also have two other projects that I've been using LLBLGen with quite happily for over a year now. I still have to maintain these projects and I'm not prepared to fully test them with the new version just yet, but moving forward, I would like to use the new version.

So my question is, can I run the two versions side by side? I know .NET is supposed to allow this without problems, but unfortunately, I have run into problems in the past with other products, so I thought I'd ask.

Thanks.



  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37866 posts
# Posted on: 24-May-2005 22:53:12.  
Well, you can Regular Smiley

Just install version 1.0.200x.y, copy it over to a folder, then uninstall it and install the latest version Regular Smiley

You only have to figure out the references of the runtimes, which obviously will have to move to the copied dir for the projects which use the older version Regular Smiley
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
jeffreygg
User



Location:
Stockton, CA USA
Joined on:
26-Oct-2003 05:53:24
Posted:
805 posts
# Posted on: 24-May-2005 23:43:51.  
This thread might be helpful. It won't help with multiple versions of the designer, but it helps with projects relying on varying versions of the runtime.

Jeff...


LLBLGen Pro Version: 2.6
Runtime Library Version: 2.6.8.1013
 
Top
billb
User



Location:

Joined on:
09-Jul-2004 21:57:41
Posted:
50 posts
# Posted on: 25-May-2005 01:46:22.  
Thanks guys. Unfortunately, I will have to have both versions of the designer as well. Hopefully this won't be the case for too much longer. As soon as I can find the time to update my existing customers to the latest version, I'll press on that way. Until then, I'll just stick with old.

jeffreygg wrote:
This thread might be helpful. It won't help with multiple versions of the designer, but it helps with projects relying on varying versions of the runtime.

Jeff...

  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37866 posts
# Posted on: 25-May-2005 09:21:21.  
As I said: you can have both designers side by side in different folders Regular Smiley. You just have to make sure your software references the right runtimes Regular Smiley. The installer wants you to uninstall older versions first, but with the trick I described, you can work around that Regular Smiley

Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
billb
User



Location:

Joined on:
09-Jul-2004 21:57:41
Posted:
50 posts
# Posted on: 25-May-2005 15:32:11.  
Why not just set the installer to not require the end user to uninstall previous versions? I figured if that was set, there was a darn good reason and I'd better not .. but with your blessing ..... Laugh

Otis wrote:
As I said: you can have both designers side by side in different folders Regular Smiley. You just have to make sure your software references the right runtimes Regular Smiley. The installer wants you to uninstall older versions first, but with the trick I described, you can work around that Regular Smiley

  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37866 posts
# Posted on: 25-May-2005 15:49:50.  
billb wrote:
Why not just set the installer to not require the end user to uninstall previous versions? I figured if that was set, there was a darn good reason and I'd better not .. but with your blessing ..... Laugh

Otis wrote:
As I said: you can have both designers side by side in different folders Regular Smiley. You just have to make sure your software references the right runtimes Regular Smiley. The installer wants you to uninstall older versions first, but with the trick I described, you can work around that Regular Smiley


I've no idea how to set that in the deployment project to be honest Regular Smiley. It's the default, I pressume.


Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
billb
User



Location:

Joined on:
09-Jul-2004 21:57:41
Posted:
50 posts
# Posted on: 25-May-2005 16:32:40.  
Actually, I think I misunderstood the "RemovePreviousVersions" flag in the installer project. When I read that initially I thought it meant that you would have to remove a previous installation to continue, but upon actually reading the help, it turns out that it will call the uninstall of the old version automatically. So ok, I'm with you, I have no idea how to set that in the deployment project. Regular Smiley

Otis wrote:
billb wrote:
Why not just set the installer to not require the end user to uninstall previous versions? I figured if that was set, there was a darn good reason and I'd better not .. but with your blessing ..... Laugh

Otis wrote:
As I said: you can have both designers side by side in different folders Regular Smiley. You just have to make sure your software references the right runtimes Regular Smiley. The installer wants you to uninstall older versions first, but with the trick I described, you can work around that Regular Smiley


I've no idea how to set that in the deployment project to be honest Regular Smiley. It's the default, I pressume.

  Top
Gabor
User



Location:
Hungary
Joined on:
29-Jan-2005 06:44:50
Posted:
97 posts
# Posted on: 23-Jan-2007 02:26:15.  
Hi,

Is it the method to use the v2.0 and v1.0.2005.1 side by side also?

Thanks

Gabor


  Top
bclubb
User



Location:
Norman, Oklahoma
Joined on:
12-Feb-2004 22:18:04
Posted:
934 posts
# Posted on: 23-Jan-2007 02:35:08.  
Yes it should work for 2005 and 2.0. If you have any problems just let us know. You will want to post in a new thread though. If you would like you can reference this post then.
  Top
absintpm
User



Location:
Greater Philadelphia Area
Joined on:
12-Jun-2007 19:04:29
Posted:
22 posts
# Posted on: 09-Feb-2009 13:06:31.  
How about those of us that don't have the option to upgrade the old projects to latest LLBLGen?

I am in this situation. And I also want/need to take advantage to latest LLBLGen releases so I found myself into position of using 3 different LLBLGen releases at the same time: 1.1, 2.5 and 2.6; They are working great being installed into different folders, except that all project files will be opened by the latest installed version. Easy to work around - use windows shell, right click on the file and chose the right version - except that all versions are listed in the shell menu as "LLBLGen" - try then to remember which one is which. Regular Smiley

Therefore, can you provide us with a way or necessary info to figure out which registry keys we need to modify in order to see in the shell menu different names for different LLBLGen versions?


AbsintPM  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37866 posts
# Posted on: 09-Feb-2009 16:56:04.  
I see what you mean, but the file associations are created with full descriptions, not with just 'LLBLGen Pro'.

So i.o.w.: the 'open with' shortcut menu in explorer, I have no idea where it gets the descriptions from. The description the file type is registered under is shown when you hover the mouse over an .lgp file and a tooltip is shown in explorer.
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
absintpm
User



Location:
Greater Philadelphia Area
Joined on:
12-Jun-2007 19:04:29
Posted:
22 posts
# Posted on: 09-Feb-2009 17:26:25.  
Yes Otis, but the file description will came up as "LLBLGen Pro v2.5 Project Files" for any .lgp file, regardless what LLBLGen version was used to create/modify that file.

However, under "open with" shell menu are listed all versions of LLBLGen. I think the links are created by windows when you first use the application (e.g LLBLGen v2.5 vs. v2.0) through the "open with" shell interface and at that time, the name listed is the application's description (Right-Click on LLBLGenPro.exe - properties - description) which in all cases is "LLBLGen Pro". Can we "fix" this somehow? Because even if I am modifying the shell commands in the registry, windows is refreshing them at startup and overrides my changes. Do you know a way to avoid that?


AbsintPM  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37866 posts
# Posted on: 10-Feb-2009 10:26:54.  
I can't find a way to do this, apparently it's not stored in the registry. So in short, you've to work with the workaround, which is starting the llblgen pro version and then from the File -> recent menu you pick the project to load.

I think in a way this is easier, as recent files are stored per version, so a project which is created with 2.0 is not available in the recent files of v2.5, which is OK, as saving it in v2.5 will make it impossible to open the file in v2.0 again.

Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
absintpm
User



Location:
Greater Philadelphia Area
Joined on:
12-Jun-2007 19:04:29
Posted:
22 posts
# Posted on: 11-Feb-2009 15:09:41.  
In this location in registry:
Code:

HKEY_CURRENT_USER\Software\Microsoft\Windows\ShellNoRoam\MUICache

I found a key with the path to each LLBLGen version installed on my machine. Modifying the value data in that key updated the links in the shell menu with the new values. And it seems those are not refreshed by windows.


AbsintPM  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37866 posts
# Posted on: 11-Feb-2009 17:44:31.  
Thanks Regular Smiley

Ive no idea what that key does but if it works, use it Regular Smiley

I'll make sure v3 etc. uses the main version number in the description.
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
absintpm
User



Location:
Greater Philadelphia Area
Joined on:
12-Jun-2007 19:04:29
Posted:
22 posts
# Posted on: 25-Feb-2009 07:56:12.  
Well, it seems that windows decided at some point to refresh those values after all. It worked fine few days (several reboots) but now my shell menu has reverted to displaying identical lines for each LLBLGen version installed. Sad

AbsintPM  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37866 posts
# Posted on: 25-Feb-2009 11:41:16.  
Hmm... then I'm out of options... Dissapointed
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.