Dotfuscator linking problem

F

Fred

Is there is a better newsgroup for this question?

I am having a problem linking assemblies into one using Dotfuscator
Pro 4.0.

The problem occurs when linking the following into one exe:
program.exe
A.dll (references C.dll, but was built when C.dll was versioned 1.1)
B.dll (references C.dll, but was built when C.dll was versioned 1.2)
C.dll (current version, 1.2)

When I run the program, I get an error saying "could not load assembly
version 1.1", and the opposite happens if I try to link in version
1.1.

Here is the actual output:

System.IO.FileNotFoundException: Could not load file or assembly
'UltraScan.Common, Version=1.20.3120.26421, Culture=neutral,
PublicKeyToken=null' or one of
File name: 'UltraScan.Common, Version=1.20.3120.26421,
Culture=neutral, PublicKeyToken=null'
at UltraScan.AMBIS.Client.USCServer..ctor()
at ModifyDemographics.Program.Process(String fn)
at ModifyDemographics.Program.Main(String[] args)

Assembly manager loaded from: c:\WINDOWS\Microsoft.NET\Framework
\v2.0.50727\mscorwks.dll
Running under executable C:\work\Apps\Utilities\ModifyDemographics
\Dotfuscated\ModifyDemographics.exe
--- A detailed error log follows.

=== Pre-bind state information ===
LOG: User = ULTRA-SCAN\kunderman_fred
LOG: DisplayName = UltraScan.Common, Version=1.20.3120.26421,
Culture=neutral, PublicKeyToken=null
(Fully-specified)
LOG: Appbase = file:///C:/work/Apps/Utilities/ModifyDemographics/Dotfuscated/
LOG: Initial PrivatePath = NULL
Calling assembly : ModifyDemographics, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=null.
===
LOG: This bind starts in default load context.
LOG: No application configuration file found.
LOG: Using machine configuration file from c:\WINDOWS\Microsoft.NET
\Framework\v2.0.50727\config\machine.config.
LOG: Policy not being applied to reference at this time (private,
custom, partial, or location-based assembly bind).
LOG: The same bind was seen before, and was failed with hr =
0x80070002.
 
D

David Goldstein

did you find a sulotion for this problem ?



Fred wrote:

Dotfuscator linking problem
09-Aug-08

Is there is a better newsgroup for this question

I am having a problem linking assemblies into one using Dotfuscato
Pro 4.0

The problem occurs when linking the following into one exe
program.ex
A.dll (references C.dll, but was built when C.dll was versioned 1.1
B.dll (references C.dll, but was built when C.dll was versioned 1.2
C.dll (current version, 1.2

When I run the program, I get an error saying "could not load assembl
version 1.1", and the opposite happens if I try to link in versio
1.1

Here is the actual output

System.IO.FileNotFoundException: Could not load file or assembl
'UltraScan.Common, Version=1.20.3120.26421, Culture=neutral
PublicKeyToken=null' or one o
File name: 'UltraScan.Common, Version=1.20.3120.26421
Culture=neutral, PublicKeyToken=null
at UltraScan.AMBIS.Client.USCServer..ctor(
at ModifyDemographics.Program.Process(String fn
at ModifyDemographics.Program.Main(String[] args

Assembly manager loaded from: c:\WINDOWS\Microsoft.NET\Framewor
\v2.0.50727\mscorwks.dl
Running under executable C:\work\Apps\Utilities\ModifyDemographic
\Dotfuscated\ModifyDemographics.ex
--- A detailed error log follows

=== Pre-bind state information ==
LOG: User = ULTRA-SCAN\kunderman_fre
LOG: DisplayName = UltraScan.Common, Version=1.20.3120.26421
Culture=neutral, PublicKeyToken=nul
(Fully-specified
LOG: Appbase = file:///C:/work/Apps/Utilities/ModifyDemographics/Dotfuscated
LOG: Initial PrivatePath = NUL
Calling assembly : ModifyDemographics, Version=1.0.0.0
Culture=neutral, PublicKeyToken=null
==
LOG: This bind starts in default load context
LOG: No application configuration file found
LOG: Using machine configuration file from c:\WINDOWS\Microsoft.NE
\Framework\v2.0.50727\config\machine.config
LOG: Policy not being applied to reference at this time (private
custom, partial, or location-based assembly bind)
LOG: The same bind was seen before, and was failed with hr
0x80070002.

Previous Posts In This Thread:

Dotfuscator linking problem
Is there is a better newsgroup for this question

I am having a problem linking assemblies into one using Dotfuscato
Pro 4.0

The problem occurs when linking the following into one exe
program.ex
A.dll (references C.dll, but was built when C.dll was versioned 1.1
B.dll (references C.dll, but was built when C.dll was versioned 1.2
C.dll (current version, 1.2

When I run the program, I get an error saying "could not load assembl
version 1.1", and the opposite happens if I try to link in versio
1.1

Here is the actual output

System.IO.FileNotFoundException: Could not load file or assembl
'UltraScan.Common, Version=1.20.3120.26421, Culture=neutral
PublicKeyToken=null' or one o
File name: 'UltraScan.Common, Version=1.20.3120.26421
Culture=neutral, PublicKeyToken=null
at UltraScan.AMBIS.Client.USCServer..ctor(
at ModifyDemographics.Program.Process(String fn
at ModifyDemographics.Program.Main(String[] args

Assembly manager loaded from: c:\WINDOWS\Microsoft.NET\Framewor
\v2.0.50727\mscorwks.dl
Running under executable C:\work\Apps\Utilities\ModifyDemographic
\Dotfuscated\ModifyDemographics.ex
--- A detailed error log follows

=== Pre-bind state information ==
LOG: User = ULTRA-SCAN\kunderman_fre
LOG: DisplayName = UltraScan.Common, Version=1.20.3120.26421
Culture=neutral, PublicKeyToken=nul
(Fully-specified
LOG: Appbase = file:///C:/work/Apps/Utilities/ModifyDemographics/Dotfuscated
LOG: Initial PrivatePath = NUL
Calling assembly : ModifyDemographics, Version=1.0.0.0
Culture=neutral, PublicKeyToken=null
==
LOG: This bind starts in default load context
LOG: No application configuration file found
LOG: Using machine configuration file from c:\WINDOWS\Microsoft.NE
\Framework\v2.0.50727\config\machine.config
LOG: Policy not being applied to reference at this time (private
custom, partial, or location-based assembly bind)
LOG: The same bind was seen before, and was failed with hr =
0x80070002.


Submitted via EggHeadCafe - Software Developer Portal of Choice
Web Service vs Web Workspace Part II
http://www.eggheadcafe.com/tutorial...6-53f6e29e3682/web-service-vs-web-worksp.aspx
 
G

Gregory A. Beamer

David Goldstein wrote in
I am having a problem linking assemblies into one using Dotfuscator
Pro 4.0.

The problem occurs when linking the following into one exe:
program.exe
A.dll (references C.dll, but was built when C.dll was versioned 1.1)
B.dll (references C.dll, but was built when C.dll was versioned 1.2)
C.dll (current version, 1.2)

When I run the program, I get an error saying "could not load assembly
version 1.1", and the opposite happens if I try to link in version
1.1.
Click to expand...


Solutions:

1. Update A.dll by recompiling
2. Update A.dll by editing the IL

As this is dotfuscator, I am not convinced you can simply set up a
config and fix it, although that does work for normal "newer version"
issues.

Your main issue here is you have your software out of sync and you are
trying to mash it all together into a single assembly. There are other
tools to do this, of course, but I am not sure they will not have the
same issue.

Peace and Grace,


--
Gregory A. Beamer (MVP)

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
| Think outside the box! |
*******************************************
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Publisher Policy - 80131040 3
Enterprise Library Issue 1
Assembly loading failure 1
BadImageFormatException with Microsoft.mshtml 1
Pb with the GAC 6
Application cant find dll even when it's in the same directory 8
asp.net err 2
VS2005 Whidbey Beta 1 FileLoadException when loading assembly 4

Top