|
Home > Archive > BizTalk Server > September 2006 > BTS 2004 strong named assembly & non-strong named assemblies
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
BTS 2004 strong named assembly & non-strong named assemblies
|
|
|
| Hello,
I have a new biztalk project where I am forced to reference an assembly that
is strong named and the assembly itself is referencing other assemblies that
are not strong named. When I build the BizTalk project I get an error and
cannot compile the BizTalk project. Does this mean that the other assemblies
that are being referenced by the strong name assembly must be strong named
also or is there a work around to this? Hopefully someone can help me with
this.
Thanks in advance, your help is greatly appreciated?
--
mj
| |
| WenJun Zhang[msft] 2006-09-16, 1:33 pm |
| Hi Marci,
What is the detailed compiling error you got when building the project in
VS?
Since you have a 'wrapper' assembly which is strong named and referenced by
your BizTalk project, you should be able to call other non-strong named
assemblies within the wrapper assembly and BizTalk will not care that.
In a more common case, you may meet errors about assembly not found when
running the application after deployment. I cannot guess the reason why
there will be problem during building. So could you please post the error
here or just send me an email? wjzhang@online.microsoft.com (remove online.)
As always, thanks for using our MSDN newsgroup & have nice weekend! :-)
Sincerely,
WenJun Zhang
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at:
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
|
|
|
|
|