I don't think there is a direct way to do this, from the brief research I did it looks like the Iran System is obsolete, though that doesn't help your problem. My advices is to create a Map which maps the numeric value of the Iranian System to the numeric equivalent in Unicode and vice versa. This isn't a huge problem but: There isn't a map type in .net, which is a pity. You can fudge it a few ways, I've done it via dictionary (it is close with key/value instead of "key"/"key"), there is a discussion here[^] Entering the numberic values by hand in code or config or somesuchis error prone. This[^] should help as there is a [almost] copy and paste value mapping Internationized text is a real pain (as I'm learning to my cost), it is even worse for right-to-left languages such as Farsi. Sort of a cross between Lawrence of Arabia and Dilbert.[^] -Or- A Dead ringer for Kate Winslett[^]

Garbage collection is probably not the answer to your question. Something is most likely holding on to your references, making it impossible to collect as garbage, even if you call Dispose(). I would use a memory profiler to find out. CLR profiler is free and easy to use. It can be found at Microsofts website: http://www.microsoft.com/download/en/details.aspx?id=16273[^] //daniel

djj55 wrote: You would need to calculate the maximum average in this query. how i could do this?

Answerred the later post. The need to optimize rises from a bad design.My articles[^]

please clear your question to justify it what is error in this code and what about exception. Mention it then we can solved it. :)

I'd start moving away from the Setup and Deployment project in Visual Studio. It won't exist in the next Visual Studio release. The supported method will be InstallShield (Lite or Express or whatever...) Windows Installer has supported x64 component since release 2.0. Normally, I'd create a seperate x64 version of the installer. But, depending on what you're doing, you may be able to do something like adding the x64 components (tagged as such) to a seperate feature, then in a CA, check the VersionNT64 property and make a call to SetFeatureState as appropriate to turn on/off its install state, in the InstallExec sequence. And you don't need any .NET code to do this. You also have to keep in mind a 32-bit installer cannot write to 64-bit registry and file locations... A guide to posting questions on CodeProject[^] Dave Kreskowiak

http://www.sql-articles.com/scripts/enabling-remote-connections-via-dos-or-t-sql[^] the actual link! THANK YOU :laugh:

mersad00 wrote: there is no info about condition compilation symbols in that link I have not used this myself but looking at the documentation I am of the opinion that you cannot add conditionals; it is assumed that they are already set in the project that is to be built. It's time for a new signature.

MS build cant build vdproj, test it!!!!!! devenv could do this! :)

MD5 is more often used for verifying that files have not been tampered with. CRC is typically for verifying transmission of data. Calculate md5 checksum/[^]

I´m sure the youngsters don´t even know the zap statement :)