Advanced Forum Search Results
-
Because I haven't hard back on this, I'll assume that there isn't a good reason for this behavior and that this is a bug in Visual Studio. I'll describe the work around that we've been working with thus far without any problems. To fix the problem, I created a post build task to copy the compiled assembly from the ...
-
Hi Jac,
Thanks for the link and your response, however, I don't think it applies to my situation. The author of that post is trying to reference a .Net assembly from silverlight where I'm trying to reference a Silverlight assembly from .Net. Like I mentioned, this was working in Silverlight 3.0 Beta 1, but seems to have broken ...
-
Upon further investigation, changing the reference to assembly 1 in assembly 2 from a project reference to a file reference appears to fix the problem. This is not an ideal solution for obvious reasons. Is there a reason for this?
Thanks,
Matt
-
I'm using the RTM of Silverlight 3.0, Visual Studio 2008 SP1, and Windows Vista. I get an error when creating a project that has two assemblies with the following structure:
Assembly 1 is a VB.Net Silverlight class library with one interface on it (without any members)
Assembly 2 is a standard VB.Net class library with one ...
-
I'm getting an almost identical issue (different class names, but same error description). Any help or response to this question will help multiple folks.
Thanks,
Matt