suugesstion need on project

Now the forums are stuttering.

Good advice by Jean and Sam!

One thing I would add is, try to get involved in a project with some senior guys who have done work and learn from there. If you do it by yourself, it may be overwhelming for you.

Cheers!

Good advice by Jean and Sam!

One thing I would add is, try to get involved in a project with some senior guys who have done work and learn from there. If you do it by yourself, it may be overwhelming for you.

Cheers!

Start by designing the application. If your college or school has not taught that then it is not a good college or school. Jean Paul's post is a start. You need to design the database in terms of tables and columns in tables and you need to design the UI; the forms for your application.

I assume you will need at least inventory, customers, orders and order items tables in the database.

My view on your project would be as following:

Instead of going for unique things - you can go for the basic features needed for an online boutique.  You can focus on the core technology areas needed to complete the project.  Once you get a confidence on the site you can add more unique features.
Otherwise, without understanding the basics there is no purpose of the project.

The core things for an online web application includes:

1) Database setup 
2) Security
3) Checkout
4) Payment
5) Above all User Interface (User Controls, Validations)
6) Exception Handling
7) Deployment

For Database setup if you already knows basic ADO.NET, then you can go for ADO.NET Entity Framework.  This will give you an idea on ORM.  

For Security, you can understand sessions and the need for cookies.  Forms Authentication is a good start here.

Payment - you can research on various payment gate ways and other options like netbanking and how to include it in your website.  Usually an upfront security deposit amount is required to enable this for the site.  As your site might be used only in college premises you can ease on this area.

For user interface, you can start with normal asp.net pages and later deal with master pages, user controls.  In this way you can also deal with lots of validation controls in ASP.NET and their impact with/without javascript.

Exception Handling gives you more control over the code and you can try with various exception handling and logging mechanisms like Enterprise Library Exception handling or if it is to heavy create a library of just writing exceptions to a file.  You can also include sending mails when exceptions occur.  This will allow you to deal with the Global.asax and application events in ASP.NET application.

Deployment involves you to learn the setup and deployment projects in Visual Studio if you are using Visual Studio IDE. There are compiled way of publishing and non-compiled way without dll's.

Please let us know if you need any further ideas/clarifications.