Hi Everyone, now, being a web padawan rather than a webmaster, i want to share you my self experiences about publishing your Asp.net web site to public

You know that those guys who are the richest computing company of the world had built some tricks o the Visual Studio 2005 Express Edition( := VS2EE) about publishing your site.

It is hard to publish your locally working, asp.net code(e.g. default.aspx) using the programs copy website feature, couse it needs the remote server to support frontpage extensions first. The second thing is to
SUPPORT ASP.NET 2.0 CODES TO WORK. MEANiNG THiS:
You have(or your system administator in the site hositing firm) to do some cool work. I first asked my system administrator to fix the problem up, but he said he had few knowledge about asp.net. He solved my first problem that was i was not able to login to my plesk( a friendly user interface that saves a webpadawans life). Plesk works in the server machine and lets u manipulate the serving, database, email, ... settings of your web site.

What i did was first he fixed the problem and i logged in to the Plesk environment. My site was giving ugly errrors saying .....(i cant remember)
ı saw the solution right there: A BUTTTON THAT ENABES YOU TO CHANGE THE .NET SERViNG OPTiONS: BY DEFAULT, ıT WAS SET TO AS.NET 1.1 AND MY FİLES WERE COMPiLED iN ASP.NET 2.0 ENViRONMENT. THE SECOND AFTER I CHANGED THE SETTiNG TOASP.NET 2.0 SERVER, SİTE WORKED FİNE

yOU MAY CHECK IF U LİKE sites Language is Turkish)
WWW.figurcercevesanatevi.com

I was in cheers that my first asp.net site was working all fine. I added some css menus for it to look better, A master page helped me so much that i did not have to write the menus in all the pages.

So u can use a ftp program such as filezilla to upload your files and your locally created site will work fine on the hosting.

You're right; FrontPage server extensions are totally unnecessary.

Microsoft lets you use "ASP Classic" and ASP.NET in the same web application, but it will only use one version of the .NET Framework. If you have access to IIS on the server, you can right click your site, go into properties, and under the ASP.NET tab you can select which version.

You can also use WebMaestro to publish changes to your site; it keeps track of which files you've changed and makes it easy to upload only them.

If you are running multiple sites on the same server you can use both 1.1 and 2.0 frameworks. Just make sure you have an application pool set up for each one.