Protecting Code [RESOLVED]

[Bolerophone]

hi,

i hv a question, suppose I am writing code for a website in ASP.NET. Now my website is hosted on some server. Now how can I make sure that my code does not stolen by their.
I do not want anyone to access my code how can I make sure??

The real situation is that our company is writing code for a govt organisation. Now they host all their pages on a common server nic.in. How can we make sure that people at nic do not misuse or tamper with our code??

[davebat]

get your own server would be the securest way

[tailz]

For starters, are you talking about the code (the .aspx.vb files) or the dll itself?

If the former then you don't need to upload them to a production server....

[Bolerophone]

If the former then you don't need to upload them to a production server....

then what would be the place to post my code then???? I guess gettting my own server is the only option.

[alex_read]

You cold code all your business logic methods within dll assemblies & just call these files from your webform codebehind pages.

If you're really paranoid, you can then use a program like Dotfuscator to protect people from disassembling your dll's and looking at the underlying code too.

[tailz]

When you talk about source, or code. I think .VB files, modules, classes etc.

When you compile an asp.net site, you get a resulting DLL and a bunch of ASPX files. Thats all that is required on the server (plus web.config) and should not exposed to prying eyes. You should not be uploading code to the site.

Also, getting your own server isn't the cheapest option (as I just discovered) but if you are paranoid about another sharer on your server, stealing and decompiling your DLL then...... I dunno just get own server.

[Bolerophone]

You cold code all your business logic methods within dll assemblies & just call these files from your webform codebehind pages.

I guess this is one option we can go with, I don't know we can do it for this project or not but for future we sure will.

Thanks all

[tailz]

I have to ask...

How is that any different from using code within the default dll assembly?

Just dont see how the code can be better protected than it already is