Monday, February 19, 2007

The Managed Code Analysis tool provides warnings that are meant to improve managed code libraries in areas such as design, localization, performance, and security. Each warning signifies a violation of a Managed Code Analysis rule. This section provides in-depth discussions and examples for each of the Managed Code Analysis warnings. The information shown in the following table is provided in the rule topic associated with each warning.

It helps in 1 stability of application2 Improves Performance3 Ease of Maintainance4 More Secure5 Follows a common naming convention for easy of understanding and gives a professional approach for applicationAnd much more...

Sunday, February 18, 2007

I had previously written, an article explaining Localization and Globalization concept in asp.net 1.3, but with asp.net 2.0 the same generalize concept of localization and globalization can be implemented more easily.

Step2: Design your form.For this example : Take 5 label controls, 4 textbox controls and 1 drop-down list control.Place the control on form as shown in figure.

Step3: Identifying Resources that needs to be localized (Globalization Phase).We want the output as shown in figure:

So here Resource that needs localization are

Language Name LabelLong Date Labelcurrency LabelAmount LabelWelcome Label (It would be same for all language, except its formatting might change, Note: you can do this easily with style-sheet concept, but as an example here I am explaining it with globalization concept.)

Now, Applying Localization to resources which needs to be localized and globalization phase. (Localization Phase begin).

Step5: Creating Resource File.For this example i am creating resource file for French and German culture and other culture would get value from default resource file. Right click the Project in Solution Explorer and add a “asp.net folder”

Add App_GlobalResources FolderAdd App_LocalResources Folder

Adding Global Resource File under App_GlobalResources Folder

Adding Local Resource File under App_LocalResources Folder

Note: While creating resource file, you should name resource file with filename.aspx.cultercode.resx

Eg:1 For Default.aspx file, Default resource file would be Default.aspx.resx

2 For German resource file for Default.aspx would be Default.aspx.de-DE.resx

3 For French resource file for Default.aspx would be Default.aspx.fr-FR.resx

Monday, February 05, 2007

From ScottGu's BlogI've seen a few people ask if it is possible to change what browser is launched and used when running web apps in VS 2005 and Visual Web Developer (for example: to use FireFox instead of IE). The good news is that there is an easy way to configure this. To-do this:

1) Right click on a .aspx page in your solution explorer

2) Select the "browse with" context menu option

3) In the dialog you can select or add a browser. If you want Firefox in the list, click "add" and point to the firefox.exe filename

4) Click the "Set as Default" button to make this the default browser when you run any page on the site.

Note that there is also an optional drop-down at the bottom of the dialog that lets you select the default browser window size when loading. You can choose 800x600 or 1024x768 if you want to visualize what the site will look like for people using those screen resolutions. This works for both IE and FireFox (and probably other browsers too -- those just happened to be the two I checked).

Most Recent Post

Community Updates

Disclaimers:We have tried hard to provide accurate information, as a user, you agree that you bear sole responsibility for your own decisions to use any programs, documents, source code, tips, articles or any other information provided on this Blog.