Here it goes:

1. Open the Microsoft Visual Studio 2008(Recommended VS2008 SP1).
2. Open a new web application project in your preferred language. I am using C#.
3. In the solution explorer, you will see default.aspx page and if we expand “Show all files”, we will see “Default.aspx.cx” and a designer file (Default.aspx.designer.cx) as well.
4. Add a App_GlobalResources ASP.Net Folder by right clicking on the “Project” and click on Add.
5. This will add App_GlobalResources folder to the Project/Solution.
6. Now, here we have to be cautious on what we add.
7. Lets add a new item to the App_GlobalResources.
8. Right click on the App_GlobalResources folder, it should automatically reflect “Resource1.resx”file.
9. Change the file name to a general name, say “Strings.resx” or “Localization.resx”
10. I will keep the name of the resource as “Strings”.
11. This will add a new resource to the App_GlobalResources folder.
12. NOTE: It is necessary to have a default resource file . Without the default resource file(in my case it is “Strings.aspx”) it is going to throw following error.

Server Error in '/' Application.

Could not load file or assembly 'App_GlobalResources' or one of its dependencies. The system cannot find the file specified.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.IO.FileNotFoundException: Could not load file or assembly 'App_GlobalResources' or one of its dependencies. The system cannot find the file specified.

Once we add a default resource, if you look into the “App_GlobalResources” folder, you will see an auto generated code.

This is what is responsible for access of the resources.

Now, as per my example, I have added a dropdown box and a label control on the page.

In the dropdown box, I have added following list items.

<asp:DropDownList ID="DropDownList1" runat="server" AutoPostBack="True"

onselectedindexchanged="DropDownList1_SelectedIndexChanged">

<asp:ListItem Value="French">French</asp:ListItem>

<asp:ListItem Value="Arabic">Arabic</asp:ListItem>

<asp:ListItem Value="German">German</asp:ListItem>

<asp:ListItem Value="English" Selected="True">English</asp:ListItem>

</asp:DropDownList>

In the Default.aspx.cx code, here is what I have added.

protected void DropDownList1_SelectedIndexChanged(object sender, EventArgs e)

{

if (this.DropDownList1.SelectedIndex == 0)

{

//French

Thread.CurrentThread.CurrentCulture = CultureInfo.CreateSpecificCulture("fr-FR");

Thread.CurrentThread.CurrentUICulture = new CultureInfo("fr-FR");

}

else if (this.DropDownList1.SelectedIndex == 1)

{

//Arabic

Thread.CurrentThread.CurrentCulture = CultureInfo.CreateSpecificCulture("ar-SA");

Thread.CurrentThread.CurrentUICulture = new CultureInfo("ar-SA");

}

else if (this.DropDownList1.SelectedIndex == 2)

{

//German

Thread.CurrentThread.CurrentCulture = CultureInfo.CreateSpecificCulture("de-De");

Thread.CurrentThread.CurrentUICulture = new CultureInfo("de-De");

}

else

{

//English

Thread.CurrentThread.CurrentCulture = CultureInfo.CreateSpecificCulture("en-US");

Thread.CurrentThread.CurrentUICulture = new CultureInfo("en-US");

}

this.Label1.Text = Resources.Strings.String1.ToString();

}

On changing the dropdown value, I set the culture for the thread and it automatically selects the respective resource based on the culture.

There you go, now you can select the culture in your page, and it is going to select the respective resource automatically.

Different ways of accessing Resources:

Retrieve Resource Values Programmatically

1. Directly accessing using the resource namespace:

We can access our resources as: this.Label1.Text = Resources.Strings.String1.ToString();

Once the default resource is added, it automatically adds a “Resources” namespace.

Within the “Resources” namespace, we see the class generated by name “Strings”. This is how we added resources to the “App_GlobalResources”, e.g Strings.resx.

So, by default, the classname generated will be “Strings”.

2. Accessing the application using ResourceManager

ResourceManager (string baseName, System.Reflection.Assembly assembly)

e.g: ResourceManager gStrings = new ResourceManager("Resources.Strings", System.Reflection.Assembly.Load("App_GlobalResources"));

Here, Resources is NameSpace, Strings is the name of the class in namespace of the resource file.

The reason I am calling “System.Reflection.Assembly.Load(“App_GlobalResources”) is because, my resource files are loaded into “App_GlobalResources” folder. By this name the dll will be generated.

In case we do not mentioned the proper namespace, as “Resources.Strings” or proper assembly name, we will get the below mentioned error message.

Implicit / Explicit localization:

Implicit localization:

If local resource files are created in Application, then implicit localization can be used to fill the property values for the control.

To use implicit localization, following naming convention must be used for resources in local resource file

key.property

Where key: Any name for the resource

Property: Property of the control that we are localizing

Ex: If we are creating resource for control label named Label1, you need to create following key/value pairs in local resource file

this.Label1.Text = "Error Message"

In aspx page, we need to use a special meta attribute in the markup for the control to specify implicit localization as-

<asp:Label ID="Label1" runat="server" meta:resourcekey="string1" Text="Label"></asp:Label>

No need to explicitly specify which properties are localized.

The resourcekey value matches a key in resource file.

At run time, ASP.NET matches resources to control properties using the resourcekey, if property value is defined in resource file, ASP.NET substitute the resource value for the property.

Explicit localization :

We use resource expression for each property of a control

For ex: A label control that is configured to set a text from global resource look like-

<asp:Label ID="Label1" runat="server" Text="<%$ Resources:ResourceFileName, String1 %>"></asp:Label>

The resource expression takes the following form

<%$ Resources:Class, ResourceID %>

Where Class: Identifies the resource file to be used

ResourceID: Identifier of the resource to be read from resource file

Versioning Satellite assemblies:

Instructs the ResourceManager to ask for a particular version of a satellite assembly to simplify updates of the main assembly of an application.

The SatelliteContractVersionAttribute establishes a contract between a main assembly and all its satellites. When the ResourceManager looks up resources, it explicitly loads the satellite version specified by this attribute on the main assembly, allowing a layer of indirection to facilitate versioning scenarios.

When the main assembly is updated, its assembly version number is incremented. However, you might not want to ship new copies of your satellite assemblies if the existing ones are sufficient and compatible with the newer version of your product. In this case, increment the main assembly's version number but leave the satellite contract version number the same. The ResourceManager will use your existing satellite assemblies.

If you need to revise a satellite assembly but not the main assembly, you must increment the version number on your satellite. In this case, ship a policy assembly along with your satellite assembly stating that your new satellite assembly has backward compatibility with your old satellite assembly. The ResourceManager will still use the old contract number written into your main assembly; however, the loader will bind to the satellite assembly version as specified by the policy assembly.

A publisher policy assembly is the way in which a vendor of a shared component makes a compatibility statement about a particular version of a released assembly. A publisher policy assembly is a strongly named assembly with a name in the format policy.<major>.<minor>.<ComponentAssemblyName>, and is registered in the Global Assembly Cache (GAC). The publisher policy is generated from an XML configuration file (see <bindingRedirect> Element) by using the Assembly Linker (Al.exe) tool. The assembly linker is used with the /link option to link the XML configuration file to a manifest assembly, that is then stored in the GAC. The publisher policy assemblies can be used when a vendor ships a maintenance release (Service Pack) that contains bug fixes.

Note:

Apply this attribute to your main assembly, passing it the version number of the satellite assembly that will work with this version of the main assembly.

       culture.
2.    If we not have UICulture="auto" set in the page directive, it will not display the culture specific UI.

3.    We can also set the culture at global level in web.config in <globalization> element under

       <System.web> element.
4.    We can have multiple App_LocalResources folder under different child folders. However we can have

       only one App_GlobalResource folder.
5.    Local resource is specific to a single Web page and used for providing versions of a Web page in

       different languages.

6.    Local resources must be stored in App_LocalResources sub folder.

7.    Local resources must be named in format <WebPageName> [.language / language and culture].resx.

8.    Ex: Default.aspx.resx- Base resource file. This is the default, or fallback, resource file. This is must

       have. e.g: Default.aspx.fr.resx- A resource file for French etc.

9.    Global resource can be read from any page or code that is in the application.

10.  Global resource must be stored in App_GlobalResources at the root of the application.

11.  Namespace used: System.Globalization; System.Resources; System.Threading

12.  The difference between resource-only and satellite assemblies is that resource-only assemblies can

      contain any resource, such as images and text. Satellite assemblies contain only culture-specific

      resources.

I will try to look for more if time permits, till then cheeers :)

C:\Program Files\Common Files\microsoft shared\Web Server Extensions\50\bin>

Type the following command.
owsadm.exe -o create -w Test1 -p 80

-o = Operation to be performed.
-w = sub web to be extended.
-p = port to be used.

You can get more help on owsadm.exe by tying owsadm.exe -help.

Here we have to make sure that the name(alias) of the virtual directory and its physical path(folder name) are same.

On IIS6, we can enabled the Virtual directory as FPSE enabled by right clicking on the Virtual directory to be extended and then click on "Configure Server Extensions 2002".

Note:- We cannot extend(FPSE) the virtual directories which are pointing to remote location/UNC share.

Reference for FPSE: https://learn.iis.net/page.aspx/134/install-frontpage-server-extensions/

Cheers :)

Resolutions:

Resolution 1. In Internet Explorer 7, uncheck the "Enabled protected mode" under the "Security" tab in IE settings for the Local Intranet Zone.

Resolution 2. In Internet Explorer 7, add the url e.g (https://localhost) to the "Trusted Sites".

Resolution 3. Run the Visual Studio 2005 as "Run as administrator".

Resolution 4. Uncheck the User Account Control (UAC) settings for the user in the control panel under User account settings(not recomended).

After installing the VS2005 SP1, the issue still persists.

However, the issue does not occur on Visual Studio 2008 and IE8.

Hope this helps :)

Cheers!

I will choose the web as my platform. Visual Studio 2008 has two modes of creating a web application.

1. Web application project

2. Websites project.

Website project model:

Create a new website.

File --> New --> New website --> ASP.Net Web Site

Once we create a new project, it will automatically add the four items in the solution. App_data folder, Default.aspx, Default.aspx.cs and web.config file. These are the default templates which are installed along with the Visual Studio 2008. These templates are located in the WebApplication.Zip folder at:

C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ProjectTemplatesCache\Web\CSharp\1033\WebApplication.zip

File name: Default.aspx

Open the WebApplication.Zip folder. Make sure you have the backup of the folder. Edit the default.aspx in the notepad. Modify the contents of the file as per the requirement and save the files. Open the Visual Studio 2008 and create a new website project. Now you should see the modified file contents in the default.aspx file in Visual Studio 2008.

When we add the new item to the existing solution, the changes made on the default.aspx page does not reflect here. It only reflects the changes when we create a new website. This is expected because the location for the item template is different.

When we add the new item to the Visual Studio solution, we have multiple options.

· Add the new item and use the code behind page.

· Add the new item and use inline code.

· Add the new item and preset the master page.

For all the three options the templates used are taken from different template locations

Option1.

Add the new item with the code behind file and no master page. The option "Place code in separate file" is checked. Go to the below mentioned location and modify the code as per requirement.

C:\Program Files\Microsoft Visual Studio9.0\Common7\IDE\ItemTemplatesCache\Web\CSharp\1033\WebForm.zip

File name: WebForm_cb.aspx

Option2.

Add the new item without the code behind file (inline code) and no master page. The option "Place code in separate file" is unchecked. Go to the below mentioned location and modify the code as per requirement.

C:\Program Files\Microsoft Visual Studio9.0\Common7\IDE\ItemTemplatesCache\Web\CSharp\1033\WebForm.zip

File name: WebForm.aspx

Option3.

Add the new item without the code behind file (inline code) and with "Select master page" option checked. The option "Place code in separate file" is unchecked. Go to the below mentioned location and modify the code as per requirement.

C:\Program Files\Microsoft Visual Studio9.0\Common7\IDE\ItemTemplatesCache\Web\CSharp\1033\WebForm.zip

File name: ContentPage.aspx

Option4.

Add the new item with the code behind file and with "Select master page" option checked. The option "Place code in separate file" is checked. Go to the below mentioned location and modify the code as per requirement.

C:\Program Files\Microsoft Visual Studio9.0\Common7\IDE\ItemTemplatesCache\Web\CSharp\1033\WebForm.zip

File name: ContentPage_cb.aspx

Web application project model:

Create a new Web application project.

Go to ... File --> New --> Project --> Project type --> Visual C# -> Web --> ASP.Net Web Application

In case of the web application project, the Visual Studio 2008 adds many default items. Properties, AssemblyInfo.cs, References, App_Data, Default.aspx, default.aspx.cx, default.aspx.designer.cs and web.config file. These templates are located at:

C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ProjectTemplatesCache\CSharp\Web\1033\WebApplicationProject.zip

Here I am going to change the default contents of the Default.aspx file. Make sure you have taken the backup before modifying the contents of the default template.

Now, let's add a new item to the project. Right click on the project and click on Add and New Item. Select the Web Form and click on the add button. When we add a new item to the solution explorer, say a new webform, we do not see the changes. This is because the item templates are taken from the different template location.

In Web application project, neither do we have inline code model nor do we have an option to preset the master page for the webform. Below is the location for the default template.

C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ItemTemplatesCache\CSharp\Web\1033\WebForm.zip

I hope this helps.

I was working with one of my customer who was trying to figure out how to check whether FTP is using SSL or not. Well, first of all I couldn't find out how exactly we can do it. But later on figured it out. In FTP log fields, there is a W3C logging field called Method (cs-method).

In order to find the difference I first used FTP without SSL and then with SSL. Below are the two logs.

Without SSL

===========

#Software: Microsoft Internet Information Services 7.0

#Version: 1.0

#Date: 2008-12-17 21:45:24

#Fields: date time c-ip c-port cs-username s-sitename s-computername sc-host s-ip s-port cs-method cs-uri-stem sc-status sc-win32-status sc-substatus sc-bytes cs-bytes time-taken x-session x-fullpath x-debug

2008-12-17 21:45:24 65.52.18.179 65491 - FTPSVC3 ComputerName - 65.52.22.60 21 ControlChannelOpened - - 0 0 0 0 0 bd8ac5be-aad1-405a-a591-49ad5cee540a - -

2008-12-17 21:45:24 65.52.18.179 65491 - FTPSVC3 ComputerName - 65.52.22.60 21 USER UserName 331 0 0 43 21 0 bd8ac5be-aad1-405a-a591-49ad5cee540a - -

2008-12-17 21:45:24 65.52.18.179 65491 UserName FTPSVC3 ComputerName - 65.52.22.60 21 PASS *** 230 0 0 21 16 46 bd8ac5be-aad1-405a-a591-49ad5cee540a / -

2008-12-17 21:45:24 65.52.18.179 65491 UserName FTPSVC3 ComputerName - 65.52.22.60 21 PWD - 257 0 0 31 5 0 bd8ac5be-aad1-405a-a591-49ad5cee540a - -

2008-12-17 21:45:24 65.52.18.179 65491 UserName FTPSVC3 ComputerName - 65.52.22.60 21 FEAT - 211 0 0 135 6 0 bd8ac5be-aad1-405a-a591-49ad5cee540a - -

2008-12-17 21:45:24 65.52.18.179 65491 UserName FTPSVC3 ComputerName - 65.52.22.60 21 REST 100 350 0 0 24 10 0 bd8ac5be-aad1-405a-a591-49ad5cee540a - -

2008-12-17 21:45:24 65.52.18.179 65491 UserName FTPSVC3 ComputerName - 65.52.22.60 21 REST 0 350 0 0 22 8 0 bd8ac5be-aad1-405a-a591-49ad5cee540a - -

2008-12-17 21:45:24 65.52.18.179 65491 UserName FTPSVC3 ComputerName - 65.52.22.60 21 PASV - 227 0 0 50 6 0 bd8ac5be-aad1-405a-a591-49ad5cee540a - -

2008-12-17 21:45:24 65.52.18.179 65492 UserName FTPSVC3 ComputerName - 65.52.22.60 59032 DataChannelOpened - - 0 0 0 0 0 bd8ac5be-aad1-405a-a591-49ad5cee540a - -

2008-12-17 21:45:24 65.52.18.179 65492 UserName FTPSVC3 ComputerName - 65.52.22.60 59032 DataChannelClosed - - 0 0 1856 0 0 bd8ac5be-aad1-405a-a591-49ad5cee540a - -

2008-12-17 21:45:24 65.52.18.179 65491 UserName FTPSVC3 ComputerName - 65.52.22.60 21 LIST - 226 0 0 1921 6 78 bd8ac5be-aad1-405a-a591-49ad5cee540a / -

2008-12-17 21:45:31 65.52.18.179 65491 UserName FTPSVC3 ComputerName - 65.52.22.60 21 ControlChannelClosed - - 1236 0 418 78 7254 bd8ac5be-aad1-405a-a591-49ad5cee540a - -

Here in these logs, we are not using SSL, therefore we do not see AUTH SSL or PBSZ entry in the logs.

With SSL

=========

#Software: Microsoft Internet Information Services 7.0

#Version: 1.0

#Date: 2008-12-17 21:46:16

#Fields: date time c-ip c-port cs-username s-sitename s-computername sc-host s-ip s-port cs-method cs-uri-stem sc-status sc-win32-status sc-substatus sc-bytes cs-bytes time-taken x-session x-fullpath x-debug

2008-12-17 21:46:16 65.52.18.179 65502 - FTPSVC3 ComputerName - 65.52.22.60 21 ControlChannelOpened - - 0 0 0 0 0 40392027-3887-4ad3-aaf2-b4d3c49c96d2 - -

2008-12-17 21:46:16 65.52.18.179 65502 - FTPSVC3 ComputerName - 65.52.22.60 21 AUTH SSL 234 0 0 22 10 62 40392027-3887-4ad3-aaf2-b4d3c49c96d2 - -

2008-12-17 21:46:20 65.52.18.179 65502 - FTPSVC3 ComputerName - 65.52.22.60 21 PBSZ 0 200 0 0 69 8 0 40392027-3887-4ad3-aaf2-b4d3c49c96d2 - -

2008-12-17 21:46:20 65.52.18.179 65502 - FTPSVC3 ComputerName - 65.52.22.60 21 USER UserName 331 0 0 69 21 0 40392027-3887-4ad3-aaf2-b4d3c49c96d2 - -

2008-12-17 21:46:20 65.52.18.179 65502 UserName FTPSVC3 ComputerName - 65.52.22.60 21 PASS *** 230 0 0 53 16 47 40392027-3887-4ad3-aaf2-b4d3c49c96d2 / -

2008-12-17 21:46:20 65.52.18.179 65502 UserName FTPSVC3 ComputerName - 65.52.22.60 21 PWD - 257 0 0 69 5 0 40392027-3887-4ad3-aaf2-b4d3c49c96d2 - -

2008-12-17 21:46:20 65.52.18.179 65502 UserName FTPSVC3 ComputerName - 65.52.22.60 21 FEAT - 211 0 0 297 6 0 40392027-3887-4ad3-aaf2-b4d3c49c96d2 - -

2008-12-17 21:46:20 65.52.18.179 65502 UserName FTPSVC3 ComputerName - 65.52.22.60 21 REST 100 350 0 0 53 10 0 40392027-3887-4ad3-aaf2-b4d3c49c96d2 - -

2008-12-17 21:46:20 65.52.18.179 65502 UserName FTPSVC3 ComputerName - 65.52.22.60 21 REST 0 350 0 0 53 8 0 40392027-3887-4ad3-aaf2-b4d3c49c96d2 - -

2008-12-17 21:46:20 65.52.18.179 65502 UserName FTPSVC3 ComputerName - 65.52.22.60 21 PBSZ 0 200 0 0 69 8 0 40392027-3887-4ad3-aaf2-b4d3c49c96d2 - -

2008-12-17 21:46:20 65.52.18.179 65502 UserName FTPSVC3 ComputerName - 65.52.22.60 21 PROT P 200 0 0 69 8 0 40392027-3887-4ad3-aaf2-b4d3c49c96d2 - -

2008-12-17 21:46:20 65.52.18.179 65502 UserName FTPSVC3 ComputerName - 65.52.22.60 21 PASV - 227 0 0 85 6 0 40392027-3887-4ad3-aaf2-b4d3c49c96d2 - -

2008-12-17 21:46:20 65.52.18.179 65503 UserName FTPSVC3 ComputerName - 65.52.22.60 59043 DataChannelOpened - - 0 0 0 0 0 40392027-3887-4ad3-aaf2-b4d3c49c96d2 - -

2008-12-17 21:46:20 65.52.18.179 65503 UserName FTPSVC3 ComputerName - 65.52.22.60 59043 DataChannelClosed - - 0 0 1930 474 0 40392027-3887-4ad3-aaf2-b4d3c49c96d2 - -

2008-12-17 21:46:20 65.52.18.179 65502 UserName FTPSVC3 ComputerName - 65.52.22.60 21 LIST - 226 0 0 2052 480 47 40392027-3887-4ad3-aaf2-b4d3c49c96d2 / -

2008-12-17 21:46:26 65.52.18.179 65502 UserName FTPSVC3 ComputerName - 65.52.22.60 21 ControlChannelClosed - - 1236 0 2005 1320 9906 40392027-3887-4ad3-aaf2-b4d3c49c96d2 - -

I have highlighted the difference in the cs-method column. In the second line we see the AUTH SSL  method. This confirms we are using SSL for the data channel. Also, PBSZ and PROT confirm that data channel is using SSL. You can refer the following link for reference(https://tools.ietf.org/html/draft-murray-auth-ftp-ssl-00)

Hope you will find it useful. ]]>