Is the Northwind Starter Kit from Codeplex a good starting point to learn more about how to best architect an ASP.NET application?
Is there something similar for the AdventureWorks database examples?
Northwind database was the best sample database for SQL Server 2000.
Talk about SQL Server 2005, AdventureWorks is better than Northwind. Northwind is not the best database due to few new features of analysis and reporting service of SQL Server 2005.
MSDN Book On Line (BOL) uses the AdventureWorks in all of their example and it makes it easy to follow up if proper understanding of AdventureWorks schema is developed.
However, SQL Server Compact Edition uses Northwind as sample database. So decide on basis of your version.
AdventureWorks database is the one that I prefer since it has a lot of advanced scenarios and is used in the samples for SQL Server Analysis Service. Analysis service is MS Business Intelligence Platform and it need to have a good amount of data for explaining the scenarios.
The NSF is not just a database sample, it has layered (domain-driven) .net examples to help developers understand a real-world implementation of various design principles (OOD, SOLID) and how those design principles are often applied via design patterns across multiple layers. So, check out NSF for more than just the Northwind database.
Related
I'm fairly new to mvc, asp.net, and .net framework in general.
I understand what models are, controllers and views, but what I don't get it is Entity Framework. I developed websites before using php, and when I needed to store some data I simply do that using MySql databases. I thought this is the case with asp.net, same concept but instead of MySql, Microsoft Sql server is used. Now I started to learn .net framework and I watched a lot of online tutorials and saw them using some classes inherited from DbContext to store data! Can anyone tell me where these classes store the data and why don't we use Microsoft Sql server instead?
Entity Framework is an Object Relational Mapping tool (ORM), a layer that sits between your database and code. The idea is that the ORM is database agnostic and will handle writing the SQL for you, so that you could (in theory) swap between SQL Server, MySQL, or whatever database you want with only configuration changes.
You can skip Entity Framework and use SQL directly with ASP.Net. Your tutorials just happen to use Entity Framework.
I'm in the market for an ASP.NET host to start learning on and to host personal projects. I've noticed most of them provided both MySQL and MS SQL databases. However, usually they will only provided a couple MS SQL databases, but a large number (like 10) MySQL Databases.
Can I use a MySQL database as a back end to a ASP.NET website? If so why would I want to pay extra to use MS SQL over MySQL?
Yes you can use MySQL to drive a website using ASP.NET or any other web development technology for that matter. The reason for choosing SQL Server over MySQL would if there were features or performance characteristics you wanted in SQL Server that did not exist in MySQL. For example, common-table expressions do not exist in MySQL. If there are no features in either that are driving your decision, then it comes down to personal preference and cost.
If you're more comfortable with Sql Server then clearly it'd be worth going down that route, for a small scale site it really does come down to personal preference. That said there are things such as the asp.net membership providers that come, by default, with support for Sql Server as opposed to MySql so that could be a deciding factor for you.
Ultimately, it comes down to personal choice. Which do you prefer and are you willing to pay if Sql Server is your preference?
I am a fresher and I have got a project in asp.net and c#. I have to create a forum, something like stackoverflow, so I have studied asp.net, c# and sql server 2008 but now I am unsure how I should start work on this project.
What technology and what part of asp.net, c# and the database will I use more? I have 3 days to study so I want to know which parts of asp.net, database and c# I have to cover in 3 days.
It's my first live project, will I have to study any other languages or are the ones listed enough?
Session management, good understanding about web controls and user control.
and just go throgh ado.net if u are using asp.net.
Maybe you should try to use ASP.net mvc check this link.
If you are going to use sql server as database / Backend of you application than
start getting infomation about linq to sql >>
LINQ to SQL: .NET Language-Integrated Query for Relational Data
or you can also go for entity framework
The ADO.NET Entity Framework Overview
I am designing an ASP.NET (3.5) web application that connects to a Rocket Software UniVerse database. I am in the planning stages right now and need some help in being pointed in the right direction. I am brand new to ASP and C#.
I am shooting for a RESTful design and a MVC pattern. Rocket provides a .NET library called UniObjects.NET which handles everything for connecting and retrieving information from the database.
What would be the best way to in general to log my users into the database, then use that session via connection pooling? I see that in 3.5 there is the ASP.NET Routing Infrastructure and that looks promising am I in the right direction on this?
Also does C# support decorators like Python and Java?
For your application I highly recommend taking a look at the official ASP.NET MVC framework (www.asp.net/mvc). The traditional ASP.NET (which is called WebForms) is clunky when it comes to true separation of concerns, dependency injection, unit testing etc. A very good starting point is:
Free End-to-End tutorial EBook "NerdDinner" - walks you through a complete application with ASP.NET MVC
As for connecting to a database: If your Database has an ADO.NET Provider you should learn the basics of accessing data via ADO.NET (http://msdn.microsoft.com/en-us/library/aa719474.aspx)
It is also recommended to use some kind of OR Mapper like NHibernate or Microsoft Entity Framework for converting relational data to the object-oriented world.
[http://en.wikipedia.org/wiki/Object-relational_mapping]
[http://en.wikipedia.org/wiki/NHibernate]
[http://msdn.microsoft.com/en-us/library/bb399572.aspx]
As this is a very broad topic, please feel free to follow up with any questions you might have. I suggest starting with the NerdDinner Tutorial.
I am a newcomer to ASP, and would like to experiment with it by writing a website for a club at my school using .net 2008 and the mySql database available from the school's apache server. What is the best way to set this up, since I see a lot of options to connect the web app to SQL Server or Oracle databases, but I'm nervous that it won't work correctly with mySql.
Also, will I still be able to use LINQ queries?
Get a hold of the MySQL Connector for ASP.NET and start coding as usual for MySQL. the connector gives you all the advantages of data adapters, data readers, etc. in the typical ADO.NET structure you are used to for SQL or Oracle. That way if you do swap things out on the back end in the future, you won't have to worry about swapping out all your connect/query code.
Check out this url: http://dev.mysql.com/tech-resources/articles/dotnet/index.html