Comments
Sort by recent activity
Jessica,
Thank you for the reply. While this did a better job, it did not do the job completely enough.
Our public method were still exposed using graywolf to view the assembly.
We tried using Agile.NET and this is accomplishing what we need. / comments
Jessica,
Thank you for the reply. While this did a better job, it did not do the job completely enough.
Our public method were still exposed using graywolf to view the assembly.
We tried using Agil...
That is perfect Brian. Thank you. / comments
That is perfect Brian. Thank you.
Is it possible to have multiple instances running simultaneously then? I am guessing not since there may be interdependencies in the projects.
I am just wondering as the obfuscation and installer build times make up the bulk of the entire build process. / comments
Is it possible to have multiple instances running simultaneously then? I am guessing not since there may be interdependencies in the projects.
I am just wondering as the obfuscation and installer b...
Jessica,
Yes, we are using 6.6 and have upgraded all the way from 4.##
I will try this tomorrow and let you know how it goes. Thanks. / comments
Jessica,
Yes, we are using 6.6 and have upgraded all the way from 4.##
I will try this tomorrow and let you know how it goes. Thanks.
No, unregistering and restarting, and registering again does not correct the issue.
If I just register without the /tlb switch there are no errors. So it is a problem in creating the type library.
Note that this is an installation deployment so having our users go through this process is definately not a solution [image]
Thanks. / comments
No, unregistering and restarting, and registering again does not correct the issue.
If I just register without the /tlb switch there are no errors. So it is a problem in creating the type library.
...
I have some more information.
This started failing when we converted our project to .NET 4.0. We have a project with Smart Assembly 6.0 and .NET 3.5 where the obfuscation and assembly registration is working correctly. However, none of our projects that we converted to .NET 4.0 work correctly.
Is there something we need to do differently for .NET 4.0 and Smart Assembly?
For now I am just skipping the smart assembly step of the build process just to get builds to QA for testing. But this is definately something I need to work on. Let me know if I need to open a formal ticket. / comments
I have some more information.
This started failing when we converted our project to .NET 4.0. We have a project with Smart Assembly 6.0 and .NET 3.5 where the obfuscation and assembly registration ...
You do realize that these installations are being tested on completely clean operating systems right? No other software other than the operating system is installed and Microsoft Security Essentials. We have multiple assemblies failing.
However, I will give this a go to see if any of our GUIDS in the .NET 4.0 assemblies are different from the .NET 3.5 for some reason, although I cannot imagine why they would be. / comments
You do realize that these installations are being tested on completely clean operating systems right? No other software other than the operating system is installed and Microsoft Security Essential...