Maybe the fact that I mentioned WPF when the OP was looking for ASP.NET was the reason. I don't see how my answer was wrong in that context as you could esily substitute the WPF front end with a ASP.NET version (or have both, and....).
I don't speak Idiot - please talk slowly and clearly
If the topic isn't something you are interested in, or have knowledge of, then you will give up on it and that won't help you. Find something that interests you and use that as a basis of your project.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
First of all this is wrong place to ask this question. Such question could be asked in GIT or Lounge.
Secondly, I appreciate the intention that you have behind posting this question i.e. learning but perhaps(like others said) you should be able to come up with some ideas on your own.
thirdly, my suggestion would be to start small application like contact book/address book or small forums. but keep in mind that your sole focus should be on learning various concepts related to C# and ASP.NET than just getting your project done.
Every now and then say, "What the Elephant." "What the Elephant" gives you freedom. Freedom brings opportunity. Opportunity makes your future.
I am trying to build an application where I can take any system remote connection(like mstsc) using .NET application. I found one windows application Remote Desktop using C#.NET[^], similarly i want to have in web application.
Or, is it possible to embedd the windows ActiveX control in web app?
Nothing wrong with that syntactically. But my preference is that if the method is more than a couple lines long, I like to break it out into it's own method so that readability and maintainability is a little easier.
If the "time consuming work" is more then a few lines, I'd say it is bad style. Its not bad style to call a method or mess around with the parameters, etc. That is often quite handy. For example, if you used the stock handler there, you couldn't pass in any arguments. Its often a lot more useful to do something like:
If you are using VS 2010 and Framework 4, use Tasks, I have not used VS 2012, so probably async is better. I like to us lambda expressons even for more than a few lines, but obviously not too many lines. What would I consider too many, maybe 10. It keeps everything together.