Search
Closed
as Not Reproducible Help for as Not Reproducible

1
Sign in to vote
0
Sign in to vote
Sign in
 to vote
Type: Bug
ID: 498991
Opened: 10/20/2009 11:38:11 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
I am facing a strange issue. I have created 5 projects in a solution which are of type Windows Class Library, Windows Console Application, Windows WPF Application, Workflow Activity Library and Sequential Workflow Console Application. I have added reference of same dll in all five projects. Without writing any code I build the projects. Three of them Windows Class Library, Windows Console Application and Windows WPF Application build successfuly while two Workflow Activity Library and Sequential Workflow Console Application projects gives this error.

XC1020: Build error occurred in the XAML MSBuild task: 'Could not load file or assembly 'assembly name' or one of its dependencies. The specified module could not be found.'

the dll i am referring to has runtime version 2.0 and setting specific version = true doesn't change anything. Not all the dlls are showing same behaviour only some of the dlls are behaving like this.

so is this issue in Vs beta version or something is wrong with Dll?
Details (expand)

Product Version

.NET Framework 4.0 Beta1
Product Language
English

Operating System
Windows XP
Operating System Language
English

Architecture
x86

Priority
(1=blocking, 2=important, 3=nice to have)
2

Severity
(1=major functionality issue, 2=important functionality issue, 3=nice to have)
2

Steps to Reproduce
Create windows worklfow activity library type project in Vs2010 beta 1. add reference to a dll. set specific version = true (dll was built on .Net 2.0 vs 2005) build the project.
Actual Results
XC1020: Build error occurred in the XAML MSBuild task: 'Could not load file or assembly 'assembly name' or one of its dependencies. The specified module could not be found.'
Expected Results
Build Succeeded
Component Usage
(any information on your scenario that may help in investigating your issue)
and If i register my assembly through gacutil in vs2010 command prompt i start getting this error
XC1020: Build error occurred in the XAML MSBuild task: 'The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)'
although i have referred same assembly in my workflow project and in Gac. also i tried by putting assembly in debug folder.

How often does this happen?
Always Happens

Have you seen this problem in other versions?
No, this is new to the most recent version

File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 10/21/2009 at 11:38 PM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Posted by Microsoft on 10/28/2009 at 1:57 PM
We are unable to reproduce this issue. Could you please attach your project to this bug that demonstrates the problem? Thanks.

Daniel Roth
Program Manager
Posted by Haris Hasan on 10/29/2009 at 10:28 AM
I have tried same thing in beta 2 now problem is not as same as it was. Now when I add the dll and build the workflow type of project it builds successfully. But when i try to create the variable using variable window in workflow designer, on selecting my class from 'Browse and select a .Net type' dialog, it gives me this error "Could not load file or assembly 'assembly name' or one of its dependencies. The specified module could not be found."

When i create an object of this class in .cs file it allows me to create and project builds successfully. But when i run that cs file, my program crashes and i get same exception "Could not load file or assembly 'assembly name' or one of its dependencies. The specified module could not be found." Note that program crashes before even execution comes inside main.

So something it is unable to find which is referenced in that dll. How can I know it exactly what it is trying to find?
© 2009 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement