The request was aborted: Could not create SSL/TLS secure channel. DNG - Getting Started

Skip to: site menu | section menu | main content

Anything and everything about Microsoft .NET technology ...
Currently viewing: Skip Navigation » ASP.NET » Getting Started - Anything and everything about Microsoft .NET technology ...


You have not logged in.



Malaika Consultants LLC
Microsoft .NET
Microsoft SQL Server
Visual Studio.NET

Email: Contact Us

Getting Started

.NET 2.0

So you want to develop ASP.NET 2.0 applications? What all do you need?

You will need to follow these steps to start developing ASP.NET applications -

Next steps

Visit the ASP.NET Developer Center. They have released a great "How Do I?" video series that walks you through the basic concepts of ASP.NET and .NET in general. They have videos showing step-by-step way of solving common everyday programming chores. It is a great way to have a look and get introduced to what all the new version has to offer. This will also give you a sneak preview of Visual Studio.NET in case you have not used it yet.

In case you are using Visual Studio.NET 2005, you will notice that the new "Create Website" template does things a little differently than what we were used to Visual Studio.NET 2003. It creates a special ASP.NET folder called as "App_Code" where all the code-behind and other business objects reside. There is also another special folder called as "App_Data" where you can have a SQL Server .mdf file which will serve as the data store for your ASP.NET application. Don't like this arrangement ? Scott Guthrie and his team have been doing a tremendous job to create the "Web Application Project model". This is not in final release mode as I understand, but it is fairly stable. There are a few known issues but nothing that is show stopping.

Update 3/20/2006:

I was making a mistake in the way I was using the above Web project model. While using the code behind I was declaring the page directive as follows:

<%@ Page Language="C#" AutoEventWireup="true" Inherits="DotNetGenerics._Default" MasterPageFile="~/DotNetGenerics.Master" CodeFile="Default.aspx.cs" %>

Why? I thought that I should use "CodeBehind" instead of "CodeFile" attribute. However when I used the "CodeBehind" Visual Studio.NET put in those green squigglies under it and informed me that the attribute "CodeBehind" is no longer supported. However what this did was when I deployed the project on the server I was getting an error on every page saying that the *.aspx.cs file was not found. I had to change the attribute to "CodeBehind" for it to be compiled in the dll. Just thought would be good to inform.

Back to top