I have an application which is in ASP.NET, ADO.NET, Oracle 11g
My structure of application is as follow
There are business entity classes for every entity in my application
Employee entity contains
a. Name
b. Age
etc
I have written a stored procedure to fetch and insert every operation related to database using ADO.NET. It return list<> of Business Entities from by separate logic part.
Some of the presentation logic is split into user-controls.
Using jquery-ajax to load most of the component for asynchronous load on pages. To speed up the page.
Have used data-caching in my project.
Not wanted to move the project into MVC 4 for better performance. Is it a good idea to move the project to ASP.NET MVC?
I also wanted to know weather it is technically ok to change it to mvc.
I don't want to change my database logic as it is well written.
So can I use MVC?
Any suggestion on any link provided will be a good help.
Related
I have to generate reports using stored procedure with passing input values to the procedure. in asp.net mvc 4,How can I achieve this?
I'm using entity framework also.so i have to do this using entity framework stored procedure.
i haven't find any useful tutorial regarding this one.
Currently i'm doing db first.
I can easily do this for standalone project c# but i havent done this for asp.net mvc project.
i did one of my project by creating data set and generate .xsd after design crystal report then load data using data set.i did this for asp.net project.
Right now actually i want to do this using stored procedure.
please let me know if there are any better mechanism to do this.
but i want to go with stored procedure.
I was looking for a best framework to develop an ASP.Net Web application.
It will be using database MS SQL Server 2000 (It has to deal with other application)
The Web server is equipped with .Net 4.0 framework
The application is mainly reading data and displaying to the user. Writing to the database is very seldome. And it should have an option to generate reports also.
Which architecture solution I should choose develop such an application?
What will be best approach?
Asp.net Webform would be easier especially if you need render report in a gridview, it also enable you to drag and drop lots of controls for fast development. You can write minimum code to achieve reading data and displaying to the user, such as defining datasource in aspx page of a gridview.
MVC on the other hand requires you to write every bit of Html by yourself, though there are some auto generated razer views, you gain more controls and get rid of viewstate, but it takes much more time to develop and learn.
You should use EF regardless which architecture you choose, it's an ORM tool for writting multi-layered applications
I am new to ASP.NET Web Forms. Now I am having a small project that I have develop it in ASP.NET. This project consists of the following:
1. data entry system: adding, editing and deleting users
2. defining two roles of the users: admin or registered user
3. creating, editing and deleting events
4. creating simple reports with some graphs
I am expert with HTML, CSS and Javascript. Also, I have a good background in C# and I used Oracle database during my university life, so I know SQL language.
I finished the Lynda Essential Training about ASP.NET and now I am thinking to start my project but I am confused about my start and I don't know from where I should start.
In addition, I have the following questions:
1. Should I know Entity Framework and know how to use it and use it in my project? Is is possible to develop the website with the SqlDataSource?
what is the best and short approach to develop this website from your experience?
Do I need to take another tutorial or is it fine to start with project and taking specific tutorial for each problem that I will face?
Your help guys is highly appreciated
There were a few decisions to make:
Project Type
Web Project or Web Application Project
See http://msdn.microsoft.com/en-us/library/dd547590.aspx
Pattern
MVC or classic Web Forms
See Biggest advantage to using ASP.Net MVC vs web forms
Data Access
Entity Framework (currently in BETA for use with Oracle, see http://www.oracle.com/technetwork/topics/dotnet/downloads/oracleefbeta-302521.html), LINQ to SQL, System.Data.SqlClient classes
can any one explain the difference between the mvc and web application in asp.net.
in mvc we can find controllers folder. cant we able to find controllers folder in web application..! please vanish my confusion.
MVC uses controllers to orchestrate the models and views to provide user interfaces to the user.
Web forms doesn't use controllers to achieve this, it uses code behind with events.
MVC is built around the notion of separation of concerns - each thing is responsible for its own bit, and shouldn't be concerned with what other bits are doing. Webforms has them a bit more mushed together, where code sits associated 1:1 with the webform (in the code behind), often leading to business logic creeping into the UI.
WebForms uses a powerful eventing system to help abstract away some of the complexities of HTTP, such as its stateless nature. MVC doesn't do this, which requires the developer to work within the confines of a pure HTTP environment. The eventing system in WebForms lets you quickly wire up events in a familiar way if you've come from a VB6/WinForms background (which the target audience had when ASP.NET was first released).
Have a look at http://www.asp.net/mvc which has a lot of great tutorials on getting started with MVC.
An ASP.NET MVC application is an application which depends upon the ASP.NET MVC Framework. MVC stands for Model, View Controller, the three components which define an application created using the MVC pattern.
The MVC pattern aims to seperate an applications logic, data and presentation into distinct, somewhat independent components.
Model
Models are a representation of an application's data. For example a shopping application might have a Cart model to represent the state of a user's shopping cart.
View
A view is a visual representation of the data contained in the model. A view class should knoow the specifics of how the model(s) it uses should be presented.
Controller
The Controller's job is to handle user input and update the state of the Model to reflect the changes that were made as a result of user action. For example imagine the user is viewing a Contact Us page and clicks the Submit button. The controller would respond to the button click by updating the model with values from the form fields and then save the model, causing it to be validated and then written to the database.
This is a very shallow and incomplete explaination of the MVC pattern you should head over to the ASP.NET MVC homepage to get a more complete view of the MVC pattern and the ASP.NET MVC framework.
An ASP.NET Web Application uses a separate framework known as Web Forms. Because Web Forms does not use the conventions defined in the MVC pattern, the Web Application template does not create a similar folder structure .
The use of either framework is not mutually exclusive, the two represent differing approaches to the same problem. With respect to which is most efficient for data access I would refere you to Michael Shimmins' excellent comment
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