Derek Stone

Did you successfully remove any previous version of Visual Studio 2005 and .NET 2.0? http://lab.msdn.microsoft.com/vs2005/uninstall/

To get this to run in Microsoft Visual Studio .NET 2003, the line "Wizard=VsWizard.VsWizardEngine" must be changed to "Wizard=VsWizard.VsWizardEngine.7.1" in the project template files.

There are numerous things wrong with this block of code: The application is not layered correctly. Entity names should reflect the entity, nothing more (drop the "Data" off of "ProductData"; rename "Product" to "Products"). A glaring SQL injection vulnerability is present (as mentioned by PlausiblyDamp). No validation is done at the property accessor level. You could easily set "ProductPrice" to -5, which makes little to no sense. Property names on business objects shouldn't include the name of the business object (change "ProductID" to "ID", etc.). Unnecessary unboxing is performed on the database fields. The collections are not strongly typed. The readers are never closed.

Please don't hijack other people's threads. I've split your posts off into a new discussion.

Bungpeng: The database fields should be defined as nvarchar and nchar. Anything stored into a String will be stored as Unicode. Therefore the only thing the application will need to do to support Unicode strings is to use the String type. It's really that simple. Do keep in mind that text direction is one of the big "gotchas" when coding globalized applications. While English might be read from left to right, Hebrew and many other languages read from right to left. Make sure to account for this in your user interface.

If you had bothered to read the entire error you'd realize the problem. The Mabry component is attempting to show a window, which obviously doesn't even make sense for an ASP.NET application.

[msdn]System.Convert[/msdn].ToBase64String()

[msdn]System.Security.Cryptography.SHA512Managed[/msdn]

They're the one control the Internet Explorer Team at Microsoft didn't reimplement. They're drawn as they're own window, "outside" of the viewport, meaning they're drawn independently of the Web page itself, and therefore not affected by z-ordering. [edit]You can view this for yourself using Spy++ or a similar application.[/edit]

[api]FlashWindow[/api]

Iterate over the Controls collection, checking the types returned.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cdosys/html/_cdosys_com_classes.asp

You can't.

You probably mean ".vbproj", not ".vdproj". That's a Visual Basic .NET project file. Try downloading Visual Basic 2005 Express.

I'd stick with the Directory / File IO / Registry forum for now. While those topics seem interesting, I doubt we'll be dedicating an entire forum to them, especially since they do fit [loosely] into an existing forum.

Yep. Stupid ain't it?

Let's keep the sarcasm to a minimum. These forums are meant to facilitate the exchange of ideas. If I wanted to listen to bickering I'd turn on some reality TV.

Turn off the UI animation. It's friggin' annoying anyway.

The forum would have to be moderated to achieve consistent subject lines.

Well gosh darn... I reckon that's a much better idea. :) [edit]Not half as fun though...[/edit]

You can find it with a simple Win32 API call to [api]GetEnvironmentVariable[/api]. Public Class Win32API 'DWORD GetEnvironmentVariable( ' LPCTSTR lpName, ' LPTSTR lpBuffer, ' DWORD nSize '); Public Declare Unicode Function GetEnvironmentVariableW Lib "kernel32.dll" _ (ByVal name As String, ByVal buffer As System.Text.StringBuilder, ByVal size As Integer) As Integer End Class Dim name As String = "ALLUSERSPROFILE" Dim buffer As System.Text.StringBuilder = New System.Text.StringBuilder(32767) Dim returnValue As Integer = Win32API.GetEnvironmentVariableW(name, buffer, buffer.Capacity) MessageBox.Show("Return value: " & returnValue.ToString()) MessageBox.Show(buffer.ToString())

[msdn]System.Security.Cryptography.RNGCryptoServiceProvider[/msdn]

This is not possible using HTML.

Make sure to use the CredUIPromptForCredentials Win32 API is if you're prompting the user to enter credentials.

You should always read this information from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders. You can't simply assume the location of directories like these.