We have been using LLBLGen successfully for a while but I have run into a problem trying to set up a new machine. The HintPath in the generated csproj file is empty for the runtime library references.

<Reference Include="SD.LLBLGen.Pro.LinqSupportClasses.NET35, Version=3.0.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27, processorArchitecture=MSIL"> <SpecificVersion>True</SpecificVersion> <HintPath> </HintPath> </Reference> <Reference Include="SD.LLBLGen.Pro.ORMSupportClasses.NET20, Version=3.0.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27, processorArchitecture=MSIL"> <SpecificVersion>True</SpecificVersion> <HintPath> </HintPath> </Reference> <Reference Include="SD.LLBLGen.Pro.DQE.SqlServer.NET20, Version=3.0.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27, processorArchitecture=MSIL"> <SpecificVersion>True</SpecificVersion> <HintPath> </HintPath> </Reference>

My command line for generating the code is:

"%ProgramFiles(x86)%\Solutions Design\LLBLGen Pro v3.0\cligenerator" %Schema%..\Mapper\SchemaMapper.llblgenproj %Namespace% C# ".NET 3.5" SelfServicing SD.Presets.SelfServicing.General2008 ..\GeneratedModel 0 %Schema%..\Mapper\Generate.Log

I'm using LLBLGen 3.0. The machine that is having the trouble is a 64 bit machine but otherwise is building the same code set.

Note: this project file did start off as a 2.6 project.

Any help is appreciated...

Thanks,

Teresa

So, if you use this is a 86x machine everything works just fine? Does the same happen if you generate from LLBLGen Designer instead of cligenerator?

Did you run the installer on the new machine or just copied over the installation folder? the hint path is obtained from the registry

It was installed but by another account on the same machine so I tried uninstalling and reinstalling but it did not help.

Also, the results are the same if I generate the code in the UI or with the command line.

Could you try to generate into an empty directory? The hintpaths aren't updated if the csproj file exists. They're only written in a new csproj file.

The HintPaths are empty even if the initial directory is empty.

I did notice that the key that was installed in the registry is

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Solutions Design\LLBLGen Pro

Could the added node in the path be an issue?

No the reg key is under HKLM\SOFTWARE\Microsoft.NETFramework<version>

There a key called 'AssemblyFoldersEx' is located, as well as an AssemblyFolders key one level higher. Below these keys, the library paths should be present. I suspect the keys were added to the 32bit registry but not the 64bit registry (which is another registry). If you run the designer as 32bit app (using the runner, see start menu) does that change (generate in empty folder, as described above)

Yes that did it!

I added the keys in the 64 bit area and now the cliGenerator works as well

Thanks for the support,

Teresa

Teresa wrote:

Yes that did it!

I added the keys in the 64 bit area and now the cliGenerator works as well

Thanks for the support,

Teresa

So we have to add that to the installer. We'll look into that

Next 3.1 installer will add the proper 64bit registry keys. They're added to the 32bit section only because the installer itself is 32bit. SetRegView in NSIS allows you to set it to the proper view of the registry to add / remove the keys

I installed v3.1 version and have issue with the HintPath. It is empty in the generated project file. This is on a 64bit windows 7 machine. I checked the registry and it looks fine. I tried both the command line and app (even the as 32bit not work). Is there any idea what could be wrong?

Thanks in advacne.

Jian wrote:

I installed v3.1 version and have issue with the HintPath

Did you get the latest installer? What is the build number?

Jian wrote:

It is empty in the generated project file. This is on a 64bit windows 7 machine. I checked the registry and it looks fine.

The 64bit registry? Do you see the reg key?

It is the latest v3.1 on the web. Build date 03/16/2011. The registries I checked are [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v2.0.50727\AssemblyFoldersEx\LLBLGen Pro Runtime Libraries v3.1] @="C:\Program Files (x86)\Solutions Design\LLBLGen Pro v3.1\Frameworks\LLBLGen Pro\RuntimeLibraries\Net2.0\"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v3.5\AssemblyFoldersEx\LLBLGen Pro Runtime Libraries v3.1] @="C:\Program Files (x86)\Solutions Design\LLBLGen Pro v3.1\Frameworks\LLBLGen Pro\RuntimeLibraries\Net3.5\"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0\AssemblyFoldersEx\LLBLGen Pro Runtime Libraries v3.1] @="C:\Program Files (x86)\Solutions Design\LLBLGen Pro v3.1\Frameworks\LLBLGen Pro\RuntimeLibraries\Net4.0\"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v2.0.50727\AssemblyFoldersEx\LLBLGen Pro Runtime Libraries v3.1] @="C:\Program Files (x86)\Solutions Design\LLBLGen Pro v3.1\Frameworks\LLBLGen Pro\RuntimeLibraries\Net2.0\"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v3.5\AssemblyFoldersEx\LLBLGen Pro Runtime Libraries v3.1] @="C:\Program Files (x86)\Solutions Design\LLBLGen Pro v3.1\Frameworks\LLBLGen Pro\RuntimeLibraries\Net3.5\"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v4.0\AssemblyFoldersEx\LLBLGen Pro Runtime Libraries v3.1] @="C:\Program Files (x86)\Solutions Design\LLBLGen Pro v3.1\Frameworks\LLBLGen Pro\RuntimeLibraries\Net4.0\"

It should have been added by the installer to the 64bit AND 32bit registry. It depends on what you use to start the designer though: it's a 32bit application by default, so when you simply start the designer, it's a 32bit app on 64bit windows and it will look in the 32bit registry.

You have the keys in both the 32bit (the WoW hive in the tree) and 64bit (normal tree in regedit) registry?

Yes. Please look the above message for registry detail.

I downloaded the source code and looked ProjectFileCreator::GetRuntimeLibraryPath(). It seems still look at v3.0 path. private static string GetRuntimeLibraryPath(string dotnetVersion) { string toReturn = string.Empty; try { // use AssemblyFolderEx system. string regKeyName; switch(dotnetVersion) { case ".NET20": regKeyName = @"Software\Microsoft.NETFramework\v2.0.50727\AssemblyFoldersEx\LLBLGen Pro Runtime Libraries v3.0"; break; case ".NET35": regKeyName = @"Software\Microsoft.NETFramework\v3.5\AssemblyFoldersEx\LLBLGen Pro Runtime Libraries v3.0"; break; default: regKeyName = @"Software\Microsoft.NETFramework\AssemblyFolders\LLBLGenPro.30.RuntimeLibraries" + dotnetVersion; break; } ... I'm not sure is this the matching source code. Also, the SD.LLBLGen.Pro.TaskPerformers.pdb is not matching the DLL.

I modified the registry to v3.0 and both the Designer and command line works.

Indeed a bug. We'll update that a.s.a.p. Sorry for the inconvenience this caused.

Fixed in next build.