Publishing in Visual Studio and then using .Net Reactor to protect it.

[mw]

Hi,

Is it possible to protect assemblies that are published in Visual
Studio using "Publish Now" in the properties of the project? I have
tried protecting the .dll.deploy files that it produces but that gives
a manifest error when trying to install. I also tried protecting the
assembly first before running publish and have difficulty doing that
for other referenced assemblies/projects. Please advise.

Thanks.

[Tim Haughton]

If you're talking about Click Once, you can't use VS. You can still do it, just script it manually.

http://msdn.microsoft.com/en-us/library/xc3tc5xx.aspx

Regards,

Tim Haughton
www.agilemicroisv.com

2008/9/11 mw <munwa...@gmail.com>

[Chad]

I'm able to do it by integrating Intellilock in a postbuild step
exactly like this:

"$(ProjectDir)postbuild.bat" "$(ProjectDir)" "obj\$(ConfigurationName)
\" $(TargetFileName)

postbuild.bat in the project folder contains:

if %2=="obj\Debug\" GOTO END
"c:\Program Files\Eziriz\IntelliLock\INTELLILOCK.exe" -project
"%~1intellilock.ilproj"
copy "%~1%~2locked\*.*" "%~1%~2" /y
:END

This way its locked when its not a debug build. But this way the
locked build is in the obj folder, which is the one that is used to
either build MSI or click ones deployments. The one you see in the
BIN folder will be unlocked but the deployed one will. You can rename
the name of the intellilock.ilproj but leave the %~1 where it is.

You should be able to slightly modify the bat file for a .net reactor
deployment.

On Sep 11, 1:16 am, "Tim Haughton" <timhaugh...@gmail.com> wrote:
> If you're talking about Click Once, you can't use VS. You can still do it,
> just script it manually.
>
> http://msdn.microsoft.com/en-us/library/xc3tc5xx.aspx
>
> Regards,
>
> Tim Haughtonwww.agilemicroisv.com
>

> 2008/9/11 mw <munwaic...@gmail.com>

>
>
>
>
>
> > Hi,
>
> > Is it possible to protect assemblies that are published in Visual
> > Studio using "Publish Now" in the properties of the project? I have
> > tried protecting the .dll.deploy files that it produces but that gives
> > a manifest error when trying to install. I also tried protecting the
> > assembly first before running publish and have difficulty doing that
> > for other referenced assemblies/projects. Please advise.
>

> > Thanks.- Hide quoted text -
>
> - Show quoted text -

[mw]

Thank you. I will give that a try.

[Denis]

As Tim indicated, there is no built-in support for the combination
protection/Click Once in VS. However there are several workarounds
(great input Chad). The .NET Reactor/IntelliLock Add-In allows you to
create a modified VS deployment project file which automatically
accesses .NET Reactor/IntelliLock at the right time to protect your
Click Once assembly.

Greetings,

Denis

[smil...@gmail.com]

I use Nullsoft Scriptable installer, and run just have a batch file I use to deploy my application.  This way I can do a whole mess of custom things like run my Nunit test protect assemblies, build installers and upload full installer and updates.

This works much better in the long run.