I am new to versioning, have a problem need help
I have 3-rd party assembly, which I wish I could attche.
If in .Net Configuration 1.1, its dependencies can be viewed. But if in .Net Configuration 2.0 (vs2005 RC), its dependencies cannot be generated due to error, but it doesn't tell you what error.
dependencies list on 1.1
mscorlib 1.0.5000.0
Microsoft.VisualC 7.0.5000.0
System.Drawing 1.0.5000.0
System 1.0.5000.0
System.Xml 1.0.5000.0
More confusing, on 2nd computer, both version Configuration tool have no problem viewing dependencies.
dependencies list on 2.0
mscorlib 1.0.5000.0
Microsoft.VisualC 7.0.5000.0
System.Drawing 1.0.5000.0
mscorlib 2.0.0.0
System 2.0.0.0
System.Configuration 2.0.0.0
System.Xml 2.0.0.0
System.Security 2.0.0.0
System.Data.SqlXml 2.0.0.0
What is the possible reason I am doing all of these because my application has problem on the 1st computer, but not on the 2nd computer.

assembly dependencies
Sean Stapleton
The reason you are seeing 2.0 .NET FRX dependencies on the second computer with .NET 2.0 installed is the roll-forward policy that is installed.
It's hard to say what the problem is without more error information. Can you take a screenshot of whatever error you are seeing, or at least the dialogs, and link to it in this post
If the assembly [your application] is built against 2.0, then the 1.1 dependency viewer may have problems analyzing it.
I may misunderstand your question. You mentioned that both Configuration tools analyzed the dependencies successfully on the second computer, but another Configuration tool failed Which tools worked on the second computer, and which failed
Also, have you tried a later build of the 2.0 FRX (e.g. an RC candidate or later CTP drop)
Hope that helps,
Stephen [Microsoft Common Language Runtime: Security - Developer]
http://blogs.msdn.com/stfisher
Pat_ON
Microsoft .NET Framework 2.0 Configuration. they are in Administrative Tools folder.
It just tells you there is an error generating the list.
tcw
The reason is the 3rd party assembly - Leadtools for .NET (based on FX 1.1) requires MSVCR71.DLL. This DLL ships with the .NET runtime 1.1 and VS 2003 but not 2.0 which has MSVCR80.DLL. Simply copying the MSVCR71.DLL file to system32 folder solved the problem.
BTW, Will the MSVCR71.DLL be included in FX 2.0 in the future
Thanks
AeQuitaZ
It is built in 1.1.4322. My application is in 2.0
Blue Stone Post
which version of .NET Framework your assembly base on 1.1.4322 or 2.0.*
If base on 2.0 your assembly will not work well on the platform of 1.1.4322
Tone Southerland
What tool are you using to check dependencies What error are you seeing You mentioned no error being shown - what behavior are you seeing with the tool
Thanks,
Stephen [Microsoft Common Language Runtime: Security - Developer]
http://blogs.msdn.com/stfisher