The Common Type System is just a set of rules that defines a commonly used set of primitive types, like System.Int32, that are used by all languages that the Common Language Runtime supports. These type are mapped to the types used in each language. For example, System.Int32 is an int in C# and an Interger in VB.NET. This makes it very easy for classes written in different languages to pass data back and forth without any custom, time-consuming, conversions. The CTS is a set of rules, or specifications, at the core of the CLR, not a module or a component. It's part of the Common Language Specification that every .NET compiler MUST adhere to to manitain compatibility with the .NET Framework. Dave Kreskowiak Microsoft MVP - Visual Basic

You can use Obfuscators to accomplish this. Vasudevan Deepak Kumar Personal Homepage Tech Gossips

He is Cool wrote: So, if I have a stand alone .NET application in a system, Ngening those .NET assemblies is recommended or not. You would definitly not NGen an assembly if it is a server application as the performace hit would only be on the first request. In general you should not NGen an assembly unless you have a very good reason to and in most cases there is no reason to. One reason to NGen an assembly would be to reduce the working set and improve startup performance but usually the overall runtime performance of your app would not be as good as if it were JITed. █▒▒▒▒▒██▒█▒██ █▒█████▒▒▒▒▒█ █▒██████▒█▒██ █▒█████▒▒▒▒▒█ █▒▒▒▒▒██▒█▒██

Damn... Beat me to it! Upcoming Scottish Developers events: * UK Security Evangelists On Tour (2nd November, Edinburgh) * Developer Day Scotland: are you interested in speaking or attending? My: Website | Blog

By cross posting you minimize your chances of getting relevant help, partly because you annoy other people, partly because you don't use the message boards in the best way. If you feel that you have to draw attention to the question from different message boards, post the question in the most relevant board, and post links to the question in the other boards. That way you get the replies in a single thread, and people can see what other have replied so that they can cooperate in helping you. --- b { font-weight: normal; }

I am dealing with something related to .NET and C# and wonder about your comment. Hope you are clear in understanding my problem.

Can u be more specific abt the problems u faced. For cross platform code usability,the general practice is to make code in c/c++,STL. Then compile/link it on diffrent platforms which ever is required. There are lots of free source code available on net which compiles with both Microssoft CL.exe and the unix/linux GCC. cheers...milton.

The AES (Rijndael) algorithm has version implemented in many languages (C / C++ / vb6 / .Net / JavaScript (I'm surprised too)) You may use that algorithm to make your cross-platform Cryptography soft. Note: Almost all (if not all) the algorithms have a ANSI C / C++ version, that means you can compile the same source in both platforms and have a "cross-platform" encryption program. Go to The Rijndael Page[^] to check the known implementations of this algorithm. I'm on a Fuzzy State: Between 0 an 1

OpenPGP[^] is an existing standard for cross-platform encryption. There are implementations for both Windows and Linux.

It shouldn't matter what code you use on each platform. If the encryption implementations are correct then it shouldn't matter if you encrypt your data on a windows box in C# and decrypt it on an old spectrum using basic. Each encryption algorithm comes with a set of test vectors that can be used to test this. The AES winner (Rjindael) is available in .NET and you can get the source online. e.gJavascript source[^]. I'll be more enthusiastic about encouraging thinking outside the box when there's evidence of any thinking going on inside it. - pTerry www.many-monkeys.com