Comments
Sort by recent activity
Normally you will create a separate SmartAssembly project for each assembly that you wish a separate output assembly for.
There is a command line version which allows more automation, but usually you will still want a separate project file for each output assembly. / comments
Normally you will create a separate SmartAssembly project for each assembly that you wish a separate output assembly for.
There is a command line version which allows more automation, but usually y...
Sorry for taking a while to reply.
We've not come across this before.
A few questions:
What framework does your assembly target, and what do the dependencies target?
Is the .NET 4.0 app calling and using the assembly in the same way as the .NET 3.5 app?
How is the assembly being called (i.e. are you using Assembly.Load(...) or similar)?
Are you getting the error message (File not found) at compile time or at runtime?
And what does the error message say - is it saying that it cannot find the assembly, "cannot find the assembly or one of it's dependencies" or cannot find one of the dependencies. / comments
Sorry for taking a while to reply.
We've not come across this before.
A few questions:
What framework does your assembly target, and what do the dependencies target?
Is the .NET 4.0 app calling and...
Just to keep you updated guys this bug is firmly listed to be fixed in the next update. I don't have a release date yet, I'll pester the developers to find out when the release date will be and if I can get an earlier copy. / comments
Just to keep you updated guys this bug is firmly listed to be fixed in the next update. I don't have a release date yet, I'll pester the developers to find out when the release date will be and if ...
Having spent a while digging in the IL code and talking with our development team, I think we have worked out why it is adding multiple version references.
If you pass a non-primitive core framework object to a method in a reference assembly which depends on a different version of the .NET framework then it will automatically add a reference to this different version.
For instance in the code you sent Eaton, there was a call to
DevExpress.XtraEditors.BaseListBoxControl.add_SelectedIndexChanged( System.EventHandler )
because the DevExpress dll was linked against the CLR 2.0 the System.EventHandler that had to be passed was the one in mscorlib 2.0 rather than the one in mscorlib 4.0 (which to the .NET framework is completely different although implicitly cast-able), so the reference was automatically added.
The developers will fix SmartAssembly so that it copes with this situation, now we know what the problem is.
Thank you very much for all your help. / comments
Having spent a while digging in the IL code and talking with our development team, I think we have worked out why it is adding multiple version references.
If you pass a non-primitive core framewor...
Eaton, I've sent you a PM. / comments
Eaton, I've sent you a PM.
Could you have look at your original (before SmartAssembly protected) assembly in Reflector and see if it is referencing two version of mscorlib.
SmartAssembly should look at the version of mscorlib referenced and from that and a few other hints link against the correct version of the framework. / comments
Could you have look at your original (before SmartAssembly protected) assembly in Reflector and see if it is referencing two version of mscorlib.
SmartAssembly should look at the version of mscorli...
Eaton wrote:
I can't look at a protected version because it gives me a build error every time.
Sorry yes.
OK, well that narrows down the problem slightly. If you have a look in the *.csproj (or *.vbproj) in notepad or similar does it mention both versions of mscorlib? / comments
Eaton wrote:
I can't look at a protected version because it gives me a build error every time.
Sorry yes.
OK, well that narrows down the problem slightly. If you have a look in the *.csproj (o...
Sorry, my fault, I meant to say the SmartAssembly project file (*.saproj or *.{sa}proj). / comments
Sorry, my fault, I meant to say the SmartAssembly project file (*.saproj or *.{sa}proj).
We don't recommend it, because it breaks error reporting, but...
Add a node called "DoNotAddPoweredByAttribute" in the "Options" section of the SmartAssembly.settings file.
However, you should really log a bug with the third party component as it is picking up the version number of a reference assembly, which is just wrong (it may as well just always return 2.0.0.0 - which could be the version of the .NET Framework core libraries). / comments
We don't recommend it, because it breaks error reporting, but...
Add a node called "DoNotAddPoweredByAttribute" in the "Options" section of the SmartAssembly.settings file.
However, you should real...
Sorry for taking a week to reply to this one, not quite sure how I missed it.
Did you start from one of the samples and edit the forms from there or did you start from scratch?
I know when I was having a play around with the samples I had a similar problem, but for that as soon as I added a resource in the Visual Studio (2010) designer everything worked.
The samples are designed for compatibility with all framework versions so the forms do not have individual resource files (they became standard in VS 2005 with the partial classes allowing forms to be kept in 3 seperate files).
If the individual resource file for the form hasn't been created by Visual Studio (or yourself), then the call to
System.ComponentModel.ComponentResourceManager resources = new System.ComponentModel.ComponentResourceManager(typeof(ExceptionReportingForm));
will fail as the ResourceManager will start off trying to resolve the ExceptionReportingForm.resource namespace. / comments
Sorry for taking a week to reply to this one, not quite sure how I missed it.
Did you start from one of the samples and edit the forms from there or did you start from scratch?
I know when I was ha...