Comments
Sort by recent activity
Yes, you are right, at one point there was another keyfile with password used in the project, which changed using SA 4.x still. Funny though that SA4 does not complain about the password it left in the project file and doesnt try to use it.
Bad though that SA doesn't ignore/reset the password when you change the key file through the GUI, even worse, when you create a new one. / comments
Yes, you are right, at one point there was another keyfile with password used in the project, which changed using SA 4.x still. Funny though that SA4 does not complain about the password it left in...
I just removed the Password= attribute from the sa project using the same keyfile without password. Works now.
Obviously there is something wrong with the password handling in SA5. / comments
I just removed the Password= attribute from the sa project using the same keyfile without password. Works now.
Obviously there is something wrong with the password handling in SA5.
Did that. Getting the same error but this time right when selecting the key file. Error report sent. / comments
Did that. Getting the same error but this time right when selecting the key file. Error report sent.
Ok, now I created a new key, directly in SA and got the same result at build time. Error report sent. / comments
Ok, now I created a new key, directly in SA and got the same result at build time. Error report sent.
Last try: created a password protected key file in VS2010, same problem when selecting the keyfile in SA. It doesnt even ask for the password. / comments
Last try: created a password protected key file in VS2010, same problem when selecting the keyfile in SA. It doesnt even ask for the password.
Well Linda, depending on your needs there actually IS a way to make it easier.
For example, I've got a set of assemblies which I pass through SA, around 15 dll's, some depending on others, some standalone. But I use the same project file for all of them. How? Hand-editing the project file including ALL dependencies into the SA project. SA chooses which of the dependencies are needed and ignores the rest. Less than optimal, but it works and makes things easier. / comments
Well Linda, depending on your needs there actually IS a way to make it easier.
For example, I've got a set of assemblies which I pass through SA, around 15 dll's, some depending on others, some sta...
On the other hand, let me throw the ball to Paul and ask: why does SmartAssembly not support merging ASP page assemblies?
Cant be that hard anymore after all the other merging its already doing. Can we have a feature request for that? :twisted: / comments
On the other hand, let me throw the ball to Paul and ask: why does SmartAssembly not support merging ASP page assemblies?
Cant be that hard anymore after all the other merging its already doing. Ca...
Gumuk, i guess your problem is that you have a lot of assemblies in your /bin folder, namely one for each asp page, so you may consider merging them into one single assembly before protecting with SA. Check out asp_merge for this job. See http://msdn.microsoft.com/en-us/library/bb397866.aspx / comments
Gumuk, i guess your problem is that you have a lot of assemblies in your /bin folder, namely one for each asp page, so you may consider merging them into one single assembly before protecting with ...
I also do not agree with this kinda silly forced update, more as I have a machine where it simply wont run after installing the "latest and greatest".
On the site red-gate states:
Why does Reflector need to update itself? This is the way .NET Reflector has always worked and is the easiest, and least intrusive, way to ensure that everyone is running the same version.
The only difference is that the "old" Reflector still worked when you didn't update. The new "you clicked No and that means no program at all" policy is really #@$!!.
What I find very disturbing is that even on machines without internet access you are forced to update or not use it. I guess that this is caused by an intermediate version which simply 'expires'.
Big :evil: for the otherwise great red-gate products. / comments
I also do not agree with this kinda silly forced update, more as I have a machine where it simply wont run after installing the "latest and greatest".
On the site red-gate states:
Why does Reflec...
I don't get any output inside Visual Studio from this build task ever. Only the infamous "error 1". Yet when I use the {smartassembly}.com instead of the build task everything works fine.
Just for reference: using Windows XP, latest hotfixes, SPs and VS2008. / comments
I don't get any output inside Visual Studio from this build task ever. Only the infamous "error 1". Yet when I use the {smartassembly}.com instead of the build task everything works fine.
Just for ...