AdditionalTypeConverterFolder with NuGet Packages

Posts   
 
    
acl
User
Posts: 91
Joined: 28-Mar-2012
# Posted on: 13-Aug-2016 13:40:50   

Hi Everyone,

I am using the LLBLGen Pro 4.0 designer for many projects. We have our own type converters that come in a NuGet package.

The AdditionalTypeConverterFolder property of the LLBLGen project is therefore set to something along the lines of "..\packages\Our.LLBLGen.Extensions.1.3.2\lib".

Whenever this NuGet Package gets updated, the path inside the LLBLGen project has to be updated too.

With 30+ projects, this can become really unnerving. Is there any alternative approach that would work better?

Best,

acl

daelmo avatar
daelmo
Support Team
Posts: 8245
Joined: 28-Nov-2005
# Posted on: 15-Aug-2016 09:20:06   

Hi acl,

You could edit the file directly (through an editor or a tool that allows you to do it this in a bulk manner. The line you should adjust is:

<Property Name="AdditionalTypeConverterFolder" Value=...
David Elizondo | LLBLGen Support Team
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39590
Joined: 17-Aug-2003
# Posted on: 15-Aug-2016 09:48:37   

or, as you own the typeconverter dll, copy them in a post-build step to a dedicated folder and specify that folder in the projects. As you seem to use the latest version of the type converter anyway (otherwise it wouldn't be a problem simple_smile ).

Frans Bouma | Lead developer LLBLGen Pro
acl
User
Posts: 91
Joined: 28-Mar-2012
# Posted on: 20-Aug-2016 17:10:40   

@daelmo: That's obviously what I'm doing.., the question is whether it is possible to set this up once and for all, so that I don't have to do this modification each time I update the NuGet package in question.

@Otis: This is sort of what we're doing now: we are pointing to the compiler output folder of the LLBLGen library DLL. (There is a small chicken/egg problem to this approach, but that's easy to get around.)

Well if there is no better solution, we'll have to leave it that way.

Thanks!