Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I have worked with window based application in .net. But I want to learn asp.net. So I want to develop one website such that developing that website I can get best and better knowledge of asp.net. And developing that website all most important concepts and controls are covered in that website. And in that website all the concept should be covered which are used in the website which are developed in today's time. So what should the website which I can develop to learn asp.net best and after developing that website I can have better knowledge of asp.net ? I have never develop a website. And which are the features that should be there in that website ? And that features are normally seen in today's website.And what are the books which I should refer ?
Update: Which are the other technologies I should also learn like javascript,css to develop better website of this time?
Make sure first which flavor of ASP.NET you want to learn:
ASP.NET webforms
ASP.NET Dynamic data
ASP.NET MVC
There are for the above mentioned technologies great tutorials which let you make up a complete site and in the mean time learn a ton from it to be found here http://www.asp.net/web-forms/fundamentals and Nerddinner.
Update: I forgot to mention the Music store sample.
Grz, Kris.
One possibility would be to pick a fairly simple database that you know well (such as Northwind or pubs) and make a web site for displaying and updating its data. This will get you familiar with data display controls such as GridView and DetailsView, and with ASP.NET databinding. You'll get to play with events and with the ASP.NET page life cycle. When you create a data entry form, you can learn ASP.NET's validators.
Once you've done that, you'll have a good foundation in ASP.NET. Most important, have fun!
Build your own blog.
Create a website that geeks from all over the world can use to meet for lunch. You could call it GeekLunch.com ;-)
I'd second XIII's answer on learning to distinguish between webforms and MVC, but if you're starting from scratch, it would be helpful to know the basics of both, to better decide which you like.
I prefer getting a big application and then reverse engineering, some prefer starting from scratch.
You already have Nerddinner for a sample MVC app.
Here are some sample webform apps:
http://forums.asp.net/default.aspx/2
They're a little dated, but the fundamentals are there.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a book, tool, software library, tutorial or other off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 8 years ago.
Improve this question
I am new to asp.net mvc. I have lot of experience in asp.net web forms. Can any one please help me find a good resource to getting started with MVC 5?
I learned .NET MVC by watching videos on Pluralsight: http://beta.pluralsight.com/. I have also learned a ton by reading posts here on Stack Overflow. There are also a lot of good learning resources on the Microsoft ASP .NET MVC site: http://www.asp.net/mvc.
In addition to all the great answers, I would like to add a few things...
As a consultant working in many different companies, I’ve had my chance to get my hands dirty on many different asp.net MVC applications.
One of the first things I realize is that people’s understanding (or lack thereof) of asp.net MVC varies a lot and this has a major impact on the way the application is built and maintained.
For the past 13 years or so, Microsoft has been teaching us how to build websites using webforms. That is by dragging and dropping controls, double-clicking it and code against that.
When asp.net MVC was first introduced (a while back), people’s initial reaction was to not fully understand why we’d want to intermingle server-side code with HTML. After all…isn’t this bad/wrong?
More importantly, people would compare this to Classic ASP and believe this is some sort of step back.
Now that more and more people have been working with asp.net MVC, I can assure you that most of them would not return to the webform style of things.
You have to understand that an asp.net MVC project is very versatile and with that versatility comes more responsibilities. It is the understanding of those new responsibilities that people don’t fully grasp. In turn, this can easily transform an MVC project into a bunch of spaghetti code and maintenance hell.
As a quick example, I’m still seeing people not understanding or seeing the benefits of having strongly typed Views with ViewModels. Applications have the tendency of evolving and change a lot. Having ViewModels will help in coping with the scalability of your application and when you need to refactor.
Try to adopt a JavaScript standard perhaps with namespace and what not as you’ll quickly see your Views contaminated with JavaScript.
Adopt the separation of concerns philosophy by having a well layered architecture not only for testability but also for ease of refactoring, maintainability and readability of your code.
As an example, download some existing application such as the open source NopCommerce project. Open the source code, see how they do things.
I think the best place to start is http://www.asp.net/mvc and also check
this PluralSight course and also Scott Allen has lots of fantastic materials on is blog google is always the best friend.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
What tools, practices, or documentation have you used in your conversion process that you would recommend to others?
You could try Microsoft's
ASP to ASP.NET 1.x Migration Assistant
The ASP to ASP.NET v1.x Migration
Assistant is designed to help you
convert ASP pages and applications to
ASP.NET. It does not make the
conversion process completely
automatic, but it will speed up your
project by automating some of the
steps required for migration.
I guess it's better than nothing.
We've converted a few ASP classic apps to .net, and are in the process of converting another.
What we did was first to split them into two groups - ones that we would convert completely, before replacing the old with the new, and then the ones we could convert incrementally.
For that second group, it was useful to build some header and sidebar controls for the app that also held some of the more programmy parts - security, navigation and such, and then use an iframe for holding the ASP classic stuff, in the areas we haven't gotten to converting yet.
It's been pretty painless, as we can pull out the old, and insert the new on our own schedule, rather than having to get the entire massive app rewritten before moving forward. It's also helped us be able to tailor the changes and new features to our customers' needs.
There is a quick and dirty way to convert from ASP to ASP.Net since ASP.Net supports inline coding that was used in ASP Classic. However, you wouldn't be taking full advantage of ASP.Net with that approach.
The bad news is there's no easy way to convert from ASP Classic to ASP.Net the "right" way. They are such different technologies there's no streamlined conversion process.
one is a scripting language and other compiled so the overall paradigm itself is completely different and I am really skeptical that there would be anyway to convert / migrate your app from classic asp to asp.net, if you intend to use asp.net the way its meant to be.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
How much of ASP.NET or C# is required for Sharepoint development? Do you need experience with things like developing N layered web applications, design patterns, test driven development, strong SQL background etc?
I hear that Sharepoint development is different from enterprise applications thats typically built with technologies like ASP.NET.
If I know my basics in .NET, C# and have some experience with ASP.NET and have good understanding of things like Page lifecycle in webforms, web parts, Master pages etc, then am I ready for Sharepoint?
Also, is Infopath very heavily used in Sharepoint development?
If you already know ASP.NET than you are ready for SharePoint development. Get familiar with its SDK and other development concepts. SharePoint Dev Wiki might also be a good start.
A must have for new developers is to learn SharePoint from end user perspective. I am using this book to train the new guys. If you do not understand these concepts it might be hard to start coding.
It really depends on what you are wanting to achive, there are more than a few ways to develop something for SharePoint each requires different skills.
for example :
SharePoint exposes a number of webservices which you can use to complete a number of tasks.
A step up from that Sharepoint has a number of DLL's you can reference directly in order to access a more granular level of detail, but is more fiddly to work with.
Neither of these require any knowledge of ASP.NET but both work with sharepoint.
If you are planning on making a WebPart then yes ASP.NET knowlege is a big plus.
If you want to work with the Sharepoint workflows then you need knowlege of WF.
There is no one fit for developing sharepoint, which quite frankly makes it hard to hire people for it.
I guess it really depends on what you mean by SharePoint development. In my humble opinion you must learn what SharePoint provides out of the box in order not to reinvent the wheel all over again.
The object model, web services and how to deploy your work using solutions is something you have to pick up very quickly in order to be a good SharePoint developer.
As I am more of a consultant type when a developer I can't say whether you should know SQL and AD but I guess it won't hurt a bit.
If you are fluent in C# it might also be a good idea to have a closer look at PowerShell as it sure looks like Microsoft will integrate PowerShell in all server products including SharePoint 2010.
I don't think it's much different, really. I've been learning both at the same time to some success. Of course, ASP.NET and SharePoint are just different things, but SharePoint is built on ASP.NET, so to the extent you understand ASP.NET, you also understand SharePoint.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
A friend of mine's company is considering using either Java or ASP.NET for web development. Currently they do all development in Delphi. As they have no experience in .NET they have asked me to come down and give a 1 hour overview of .NET (mainly ASP.NET). What topics should I cover?
I was hired by a Delphi product company as a senior .NET developer with the goal of moving their applications from Delphi client server/desktop apps to web based ASP.NET.
I no longer work there but remain friends with an experienced Delphi programmer who is still there.
The biggest concern you have is ensuring that these Delphi programmers start to get their heads around the fundamental shift from desktop client server apps (very common using Delphi) to web based stateless, cross browser UI ASP.NET.
My friend from the previous company has said that the company is still struggling along with minimal .NET progress after 2 years. Technologies such as XML, Javascript, AJax and even fundamentals such as the .NET CLR and assemblies are still a bit of a mystery to the team.
In summary, if I was you I would be focusing entirely on bigger concepts such as the stateless nature of the web and how ASP.NET can solve it, and the benefits and drawbacks of thin client software (ie ease of deployment, browser incompatibilies, less rich user interfaces etc.)
Other than the other suggestions you are no doubt going to get, I'd explain to them that there is a Delphi for .NET which would ease the pain of change a little. So basically they are using Delphi as the language but the underpinnings of .NET.
You might want to talk to your regional developer evangelist. I'm sure they have a stack of bullet points for instances just like this.
You can find your local evangelist(s) at: http://msdn.microsoft.com/en-us/bb905078.aspx
There is so much to cover!
ASP.Net is better for Web Development though, It is designed for it. Take into account the following features:
Membership Provider
ASP.Net controls
The Whole Page and Code-Behind
system and don't forget ASP.Net MVC
ASP.Net Ajax and support for jQuery
ASP.Net peforms well generally, not
sure about Java though
Use .Net Librarys and languages, C#
or VB.Net and so on.
Many Many more
I would cover those, the way ASP.Net is designed as a much more complete package for web development than Java is. I also think the connection between pages and code is better in ASP.Net than using PHP/Java or how ever they would do it.
Can also switch to Winforms or other MS technologies relatively easily.
If they do want to explore C# the transition is pretty easy. Just remind them that Anders Hejlsberg was the Chief Architect of Delphi and C#.
http://en.wikipedia.org/wiki/Anders_Hejlsberg
I was a VB.net guy, but I took a one year Delphi gig a few years back. When I came back to .Net I was using C# and the transition was very easy.
Not sure if you're planning to give more of an architectural view or a more of hands-on experience (say, build a demo Hello World ASP.NET site), but anyway, here are some topics that might get them interested:
.NET covers many languages (C#, VB.NET, IronPython, IronRuby, Delphi.NET), even on the same solution; that means the developers can reuse some of their previous knowledge;
To support the item above, an overview of the CLR, IL etc might be useful, maybe comparing it a bit with how Java works
Visual Studio.NET is a great IDE, and there are lots of tools for it that support the latest best practices (TDD, IoC etc), including OSS
Could be also nice to mention Mono (maybe show them the same app running on Windows, MAc and Linux?) and ASP.NET MVC, in case your teammates have some knowledge of what MVC, RoR are about
I will think some more... :)
First off I'd give them a tour of creating a simple web app using Visual Studio and whatever the equivalent would be in Java. Seeing it done speaks a lot more than just giving the theory.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I would like to know your experience with ASP.NET webparts as a reusable component in your website.
How useful did you find it? Did you find any serious issues with it? Would you recommend it using in any asp.net project?
Any best practices or tips you would like to highlight with respect to this.
Would you recommend using webparts as part of the asp.net portal design or would our center your design around our good old UserControl as the foundation.
This input would help me make my decision for an asp.net application that I am developing.
In case you require more clarification please do leave comments.
Advantages of WebParts over UserControls:
Support for user editable properties and personalization built in
Customizable Editor Parts
Customizable standard WebPart menus
Drag'n'Drop WebParts between WebPartZones
Support for connections between WebParts, useful for master/detail views, filters, and more
Can load UserControls
Disadvantages:
Higher Resource Usage
Visual Studio currently does not have designer support for WebParts
Like ocdecio mentioned, ASP.NET MVC would probably be a better choice nowadays, at least outside of the SharePoint world, where WebParts are very important.
EDIT:
For an overview of ASP.NET 2.0 WebParts, you may want to look at:
Using WebParts in ASP.Net 2.0 and
Personalize Your Portal with User Controls and Custom Web Parts
I personally wouldn't recommend WebParts for your application unless you are going to go full-blown into the webparts portal paradigm. I played around with them sparingly and it just doesn't feel like it would be as effective as designing your own pieces.
In my experience web parts are useful to create content for SharePoint. But now with ASP.NET MVC I'm not sure they will be a good choice for a standard ASP.NET application.
I agree with TheTXI...like a lot of ASP.NET technologies, you aren't really going to get much benefit from Web Parts unless you buy into the model 100%.
But aside from that, we had some technical issues as well, mainly related to cross-browser UI rendering problems. These might have been fixed in recent releases, I don't know: we ended up rolling our own solution.
ASP.NET MVC is getting so much traction. It is literally blow everything else out of the water. I would recommend look into that first. Sharepoint probably will incorporate MVC very soon.