Support forum of the software localization tool Sisulizer


.NET, Delphi, ... - Sisulizer Localization Tool Support Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.

Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 

 Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius
New Topic Reply Printer Friendly
WPF Error: Cannot resolve dependency to assembly because it has not been preloaded - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Thu Nov 22nd, 2018 02:02 am
PM Private Upload Quote Reply
ngallimore
Member
 

Joined: Wed Nov 11th, 2009
Location: Brisbane, Australia
Posts: 26
Status: 
Offline
Hi,

We're trying to localize a new WPF application, and we're getting the following error during generation of the resource assemblies:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.WinFx.targets(268,9): warning MC1000: Unknown build error, 'Cannot resolve dependency to assembly 'Rpm.Registration, Version=1.0.5.0, Culture=neutral, PublicKeyToken=71e377773cc66c4c' because it has not been preloaded. When using the ReflectionOnly APIs, dependent assemblies must be pre-loaded or loaded on demand through the ReflectionOnlyAssemblyResolve event.'  [D:\Projects\Scheduling\Workspace Explorer\Dev\Trunk\Source\Workspace Explorer\Workspace Explorer\Workspace Explorer.proj]


That DLL is in the output folder of the project so it should be able to be found. We successfully localize quite a few other WPF applications (including others that use that same DLL) without any problems so I'm at a bit of a loss as to the cause of this problem.

I've uploaded the dump of the details that Sisulizer generates.

Any assistance on tracking down the cause would be much appreciated.

Thanks,
Nick Gallimore

Back To Top PM Private Upload Quote Reply

 Posted: Thu Nov 22nd, 2018 09:45 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3165
Status: 
Offline
Hi Nick,

Sounds like it can not reference that DLL. Do you know this:

https://stackoverflow.com/questions/7253740/unknown-build-error-cannot-resolve-dependency-to-system-windows

The top answer on this page might be a hint in your case as well.

Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Thu Nov 22nd, 2018 09:32 pm
PM Private Upload Quote Reply
ngallimore
Member
 

Joined: Wed Nov 11th, 2009
Location: Brisbane, Australia
Posts: 26
Status: 
Offline
Hi Markus,
Thanks for the response. Unfortunately I don't believe it's the same issue.
The error is happening when Sisulizer attempts to generate the satellite resource assemblies (the main project compiles fine in Visual Studio). The DLL in question is in the output folder and is referenced by the project that Sisulizer generated and tries to compile (included in zip file).
Forgot to mention in the original post, using latest version, 4.0 build 373.
Thanks,Nick Gallimore

Back To Top PM Private Upload Quote Reply

 Posted: Thu Nov 22nd, 2018 09:58 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3165
Status: 
Offline
Hi Nick,
I wonder since you said the very same DLL is working in other projects. Sisulizer uses the same tools VS uses to build the project.

I have to forward this to our R&D and see if they can sort that out.
Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Tue Dec 4th, 2018 02:32 am
PM Private Upload Quote Reply
ngallimore
Member
 

Joined: Wed Nov 11th, 2009
Location: Brisbane, Australia
Posts: 26
Status: 
Offline
Hi Markus,


I’ve done some more investigation and narrowed the issue down somewhat. First some background: for a number of reasons we don’t use hint paths on individual assembly references within CSPROJ files, we centralise those paths within a separate MSBuild targets file by specifying the MSBuild AssemblySearchPaths property. This makes it easier to update when the paths change, and hasn’t caused any problems with Sisulizer in the past.


I’ve noticed in this particular case, for some reason Sisulizer is not outputting the hint path in the generated PROJ file, and so the compiling of the XAML files into BAML fails in cases where the XAML references types contained within dependant DLLs. I manually added hint paths to the assembly references in the parent CSPROJ file and sure enough Sisulizer started working. Now given this is working elsewhere without having to do this, I’d rather get to the bottom of why it’s different in this case than to sprinkle hint paths around.


I took an existing project that is set up the same way, deleted that same DLL from the output directory of that project, then ran it through Sisulizer. Sure enough Sisulizer failed with the same error, and I could then check the PROJ file that was generated there. Every assembly reference other than the system ones had a hint path, other than the DLL that I removed. So Sisulizer generating a hint path for an assembly reference does not require the source CSPROJ file to contain a hint path for that reference.


To confirm again: the DLLs are all in the project’s output folder, so they should be able to be found there.


I did try setting the assembly directory property on the solution within Sisulizer, which the Sisulizer documentation suggests should help Sisulizer to locate the assemblies, but that didn’t help at all.


So, two questions:
1. What would cause Sisulizer to fail to add a hint path to the generated PROJ file when the DLLs are in the output directory for the CSPROJ?
2. What does the assembly directory property in Sisulizer do (specified within the properties dialog of a VS Solution, on the File tab)? The documentation suggests it should help in this case, but it doesn’t appear to.


Thanks,
Nick Gallimore

Back To Top PM Private Upload Quote Reply

Current time is 10:20 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > WPF Error: Cannot resolve dependency to assembly because it has not been preloaded



WowUltra modified by Sisulizer Copyright © 2007-18 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Impress - Privacy statement

Sisulizer software localization tool - Three simple steps to localize