Just specify a current culture in your web.config file. In this case we specify it on an application level:
<configuration>
<system.web>
<globalization culture="nl-BE" uiCulture="nl-BE" />
</system.web>
</configuration>
It is as easy as that :)
So when you now execute the following code:
now.ToLongDateString will return maandag 28 februari 2005 (instead of monday...)
Read it all here
- Ken
I went to the AutoRai in the Netherlands (Amsterdam) yesterday. Hamburg-Mannheimer invited me to the Jaguars' VIP room.
A lot of amazing sportcars! The Ferrari enzo (+/- 990.000 €), Porche Carrera GT and also my dreamcars 'Dodge Viper' and 'Honda S2000' (see image below).
View the entire image gallery.
- Ken
It's usefull to show the version information in your application.
In your AssemblyInfo.vb file you can set the version information.
<
Assembly: AssemblyVersion("1.1.0.0")>
Full Version Number
A full, three-part number indicating a specific implementation. This is specified in a.b.c format.
Major Release Number
The first number is the major release number (that's the a). All beta software will start with 0. Once the software is ready for a first release it will be go up to 1: ie. 1.0.0. And every major rewrite of the software will increment by one. A major release should have a high-level set of specific goals that it is meeting.
Minor Release Number
The second number is the minor release number (that's the b). The minor release number will tell you whether a release is a stable or development branch. Even numbers (0, 2, 4...) mean that it's a stable release, and odd numbers (1, 3, 5...) mean it's a development release. A minor release should have a lower-level set of specific goals that it is meeting. These goals should, somehow or another, be a subset of the goals for the major release of which it is a part. Basically, the minor releases allow for the major goals of a major release to be broken into a more discrete, attainable set of objectives.
Release Increment-or
Lastly, the final number in a three-part version number is a release increment-or (that's the c). In a stable branch, new versions will be release as bugs are found and squished. In a development branch, new versions will be released as progress is made toward the goals set for the next major and minor release. New releases will happen as needed in a stable branch. In a development branch, however, they should happen frequently, as more progress is made toward the next minor release.
In your application, you can get the version info:
System.Reflection.Assembly.GetExecutingAssembly.GetName.Version.ToString()
You can find more infor on MSDN
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemReflectionAssemblyVersionAttributeClassctorTopic.asp
- Ken
You can run each control on your asp.net pages at server side.
In this case a little sample with the body tag.
Html:
<body ID=BodyTag runat=server>
Code:
Protected WithEvents BodyTag As System.Web.UI.HtmlControls.HtmlGenericControl
...
BodyTag.Attributes.Add("onLoad", "window.close()")
...
In this sample, your page with automatically close.
- Ken
For the dotnet6 fans, you can now order your own dotnet6 t-shirt.
- Ken