visual studio extension reports version issue

Posts   
 
    
morten71
User
Posts: 80
Joined: 13-Jan-2009
# Posted on: 06-Oct-2014 11:15:02   

I just installed the Oct. 3rd 2014 build of LLBLGen Pro v4.2 During the installation the VS extenstion is installed (alright, however, I'd like to have this installation as an option).

When I start VS2013 I'm notified that "An update to LLBLGen Pro" is available.

In my VS2013 Extenstions and Updates -> Updates -> Visual Studio Gallery LLBLGen Pro details displays "Current Version: 4.0". "New Version: 4.2".

The "More information" link takes me to http://visualstudiogallery.msdn.microsoft.com/e83a4238-7169-4d2c-9729-0462b55a30e1?SRC=VSIDE (VS > Extensions > Tools > LLBLGen Pro).

The "Get now" button takes me to http://www.llblgen.com/Pages/trial.aspx (from where I originally downloaded the version :-|

Anyways, thanks for a great tool I keep learning about.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 06-Oct-2014 15:54:59   

An explanation why this happens can be found here: http://www.llblgen.com/tinyforum/GotoMessage.aspx?MessageID=130292&ThreadID=23003

We're thinking about setting the version on the gallery back to v4.0, as it's gives problems now.

Frans Bouma | Lead developer LLBLGen Pro
morten71
User
Posts: 80
Joined: 13-Jan-2009
# Posted on: 06-Oct-2014 17:28:39   

Otis wrote:

An explanation why this happens can be found here: http://www.llblgen.com/tinyforum/GotoMessage.aspx?MessageID=130292&ThreadID=23003

We're thinking about setting the version on the gallery back to v4.0, as it's gives problems now.

Thanks for your reply. And I see. Still, if possible, the option to de-select the VS extension during setup would be appreciated.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 07-Oct-2014 10:04:30   

morten71 wrote:

Otis wrote:

An explanation why this happens can be found here: http://www.llblgen.com/tinyforum/GotoMessage.aspx?MessageID=130292&ThreadID=23003

We're thinking about setting the version on the gallery back to v4.0, as it's gives problems now.

Thanks for your reply. And I see. Still, if possible, the option to de-select the VS extension during setup would be appreciated.

As in... you don't want the integration support?

Frans Bouma | Lead developer LLBLGen Pro
morten71
User
Posts: 80
Joined: 13-Jan-2009
# Posted on: 07-Oct-2014 12:09:15   

Otis wrote:

morten71 wrote:

Otis wrote:

An explanation why this happens can be found here: http://www.llblgen.com/tinyforum/GotoMessage.aspx?MessageID=130292&ThreadID=23003

We're thinking about setting the version on the gallery back to v4.0, as it's gives problems now.

Thanks for your reply. And I see. Still, if possible, the option to de-select the VS extension during setup would be appreciated.

As in... you don't want the integration support?

I like it, however, I also like my VS clean and options (feeling of) when installing tools, and I mostly use the windows gui.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 10-Oct-2014 11:55:17   

We'll look at the conditionally integration support in the installer in the next version of the designer.

About the version number. We investigated whether we could do a conditional compilation of the extension, so the one shipped with v4.0 showed v4.0 (and thus would result in the message from vs.net that a new version was available), the one in v4.1 showed v4.1 etc. This turned out to be impossible! Conditional compilation is not hard, however vs.net extensions have a manifest file, which is xml. Xml doesn't have conditional compilation statements so we created a couple of these files, each with a different version number and used different csproj files to use the right one. This didn't work, as the vs.net sdk has the manifest filename hardcoded in its targets: source.extension.vsixmanifest.

So we thought: let's copy the file required over the existing source.extension.vsixmanifest, then it should work, right? Well... no. During build the vsix compiler copies the extension to the experimental hive: however if there is already a build with a higher versionnumber there, it can't continue as it can't 'remove' the one there and crashes with an error.

I.o.w.: this system of integrating inside vs.net is so broken it's beyond repair. (FUBAR wink ).

So we changed the version number in the gallery to v4.0. This sucks too, but at least users won't get a popup that a new version is available while you already have the latest installed.

Frans Bouma | Lead developer LLBLGen Pro
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 10-Oct-2014 16:09:30   

@Pilchie (vs.net team member) came with the suggestion to pass

/p:DeployExtension=false

to MSBuild, and this indeed fixes that last crash.

We already reverted our changes (as it was no use to keep them around), so we'll try again on monday simple_smile (with the file copy crap).

Frans Bouma | Lead developer LLBLGen Pro
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 04-Nov-2014 16:46:29   

This has been postponed to v5. The version of the gallery is v4.0 to avoid a popup for v4.1 users who know there's an update but can't upgrade for whatever reason.

Frans Bouma | Lead developer LLBLGen Pro