I am asking my self many times before start writing a new app or data access library , should I use LINQ to SQL or classic ADO.net , I have used both and the development time I spend on building an app with LINQ to SQL is like the 1/3 compared to ADO.net.
The only think I like using LINQ to SQL is that I don't have to design the domain objects LINQ does that for me and saves me from spend my time on boring things :P But is LINQ to SQL suitable for large scale projects, is there an overhead that we can avoid when using ADO.net ?
I am new to ASP.Net. I am working on an ASP application in which I need to use an existing C# class (.cs) to get a return and pass to my ASP code. I know it may be impossible to call C# class directly from classic ASP.
Just two many pages to re-write. A Microsoft consultant informed us it would cost about $750,000 to rewrite all of our pages. The school district's budget is only $67,500 so this is out of the question. Therefore I am going to have to stick to asp Classic.
I currently work for a company that uses a combination of ASP.NET Webforms and legacy ASP pages for web development. This works fairly well for their current projects but I would like to convince / suggest to them to switch over to ASP.NET MVC since most of their codebase consists of wiring form elements to stored procedure parameters. Just using an ORM is also a possibility but I think it would be a good idea to use this opportunity to switch to an MVC framework.
However, I'm not sure how easy it will be to deploy an ASP.NET MVC app along side ASP.NET and Classic ASP code while the codebase is updated. First, I would like to ask if this is even possible. I've seen threads about running ASP.NET with Classic ASP and ASP.NET MVC with Webforms but not all three in the same application. They currently have Webforms and Classic ASP working together so the pitfalls associated with that are already solved.
I'm migrating a site from classic asp to asp.net 4.0
Before I rework all the code, I wanted to get clarification that the way i think my database code should be updated is fairly correct. (I'm using SQLClient objects)
First, when old code would use forward only recordsets or access single record/value, I'm fairly sure i'd use SqlCommand and SqlDataReader. That is pretty straightforward.
Now, when my old code navigates a recordset (movePrevious, find, etc.)... I believe the way to go is with SqlDataAdapter and DataTable to retrieve the data and DataView to filter/find/navigate the data.
I'n looking to do a quick migration... i don't want to get too bogged down in the new entity framework... so - just trying to stick with similar objects/logic.
I know this is one of those questions that doesn't really have a right/wrong answer... and I think that is part of my problem in finding an answer - there are so many.
some automated tools to help in migrating classic ASP to ASP.NET I tried to install "ASP to ASP.NET 1.x Migration Assistant" from the link below but it encountered a problem during installation. Has anyone used it? Any other better tools? I know everything cannot be automated but I would imagine there are some tools out there. [URL]
We are in design phase of a project whose goal is replatforming an ASP classic application to ASP.Net 4.0. The system needs to be entirely web based. There are several new requirements for the new system that make this a challenging project:
The system needs to be database independent. It must, at version 1.0, support MS SQL Server, Oracle, MySQL, Postgres and DB2. The system must be able to allow easy reporting from the database by third party reporting packages. The system must allow an administrative end user to create their own tables in the database through the web based interface. The system must allow an administrative end user to design/configure a user interface (web based) where they can select tables and fields in the system (either our system's core tables or their own custom tables created in #3) The system must allow an administrative end user to create and maintain relationships between these custom created tables, and also between these tables and our system's core tables. The system must allow an administrative end user to create business rules that will enforce validation, show/hide UI elements, block certain actions based on the identity of specific users, specific user groups or privileges.
Essentially it's a system that has some core ticket tracking functionality, but allows the end user to extend the interface, business rules and the database. Is this possible to build in a .Net, Web based environment? If so, what do you think the level of effort would be to get this done? We are currently a 6 person shop, with 2.5 full time developers.
I am new to ASP and ASP.net.I have just started working on a legacy ASP classic project and been given a sample that makes a remote call in ASP.net.Is it possible to call the ASP.net page from ASP?Are you they compatible.My impression so far is that they aren't compatible, but perhaps. I'm wrong.I mean the .net project could be called with parameters and kept seperate I guess?Does anyone have any experience with similar problems or have any tips they can share?
We have a big classic ASP website, and we want to start writing new code in .net, (the website is way to big to rewrite 100% at this stage).
The old website uses session variables, will these still be accessible in the .net pages, and if not (which I suspect) is there anything we can do to make them accessible?
The new section is detachable, that is it is pretty much independent from the rest of the site so should be fine to write in .NET, it's just sessions which are important to us. Do we need another login page?
How bad practise would it be to ajax a local .net page which sets session info when they login to the old site? Can we copy session data this way?
I know S#arp architecture is built for ASP.NET MVC. But I'm wondering if it can be used in classic ASP.NET (WebForms) or even desktop applications like WinForms or WPF.
how I can include .inc file from VB classic ASP in C# aspx page?
I try do it with:
<!-- #include file="menu.inc" -->
But I receive error about syntax in menu.inc "Compiler Error Message: CS1003: Syntax error, '(' expected" - "Line 3: if Len(Session("GUID")) < 1 Then": <% if Len(Session("GUID")) < 1 Then Response.Redirect "default.asp" End If %>
We have a site and a logged in section of the site that all was written in classic asp. We are starting to convert the site pages to asp.net 3.5. We are starting with the easiest pages (text mainly) first then we will rewrite the web application part of the site.
My question is - Is it possible to run the new asp.net 3.5 pages with classic asp pages? Or will we need to rewrite everything before deploying?
For some reason, the response.redirect seems to be failing and it is maxing out the cpu on my server and just doesn't do anything. The .net code uploads the file fine, but does not redirect to the asp page to do the processing. I know this is absolute rubbish why would you have .net code redirecting to classic asp, it is a legacy app. I have tried putting false or true etc. at the end of the redirect as I have read other people have had issues with this. it runs locally on my machine but won't run on my server! I am getting the following error when I debugged remotely.
I have an asp page with an input/text field and an anchor/href that links to an aspx page. What I want is to populate the label control on my aspx page with the value entered in the input/text field. How would I do that?
I will be adding new pages and adding functionality to current pages.
I would basically like to use new technology and but I don't know how should I add it to classic ASP pages
In other words, can I <#--include--> an aspx page in Classic asp page? Or anything of that sort, may be creating a user control in ASP.NET and using it in classic ASP?
I am trying to convert existing classic ASP webpages to ASP.NET. I dont have a lot of knowledge in the area. This is what i currently have. I use a Microsoft Access to pass data to tables in a Oracle Database. I then have .asp pages that pull data from the oracle tables. I just recently installed Visual Studio 2010 Ultimate and i want to start converting my .asp pages to .aspx. I have never used Visual Studio before so I am stuck at the beginning of this process. Do i start by creating a new ASP.NET Web application? I know there are things i need to add to the Webconfig file too but i dont know exactly what.
I am making MSSQL stored procedure CLR calls from ASP pages. When an exception occurs, it is logged and then rethrown. In this scenario I need to be able to handle the exception (if possible) in the ASP page. Note that I cannot move away from classic ASP in this instance; I am stuck within a legacy system for this project. let me know if you know of a way to handle the exceptions in classic ASP.
You can define a view in MVC 2 the following code and have only one form to handle all events.I can not use the classic button, because it required the use of images.
Are you experienced with both ASP.NET and WPF coding? If so, I'll be grateful if you'll share your experience, We are estimating a 100-screen WPF project. Our estimation methodology involves characterizing the complexity of each screen. We then apply a standard number for the development time, based on the complexity and the technology. The standard number is based on the developer being good, not a super-star.
I am using StructureMap with ASP.NET MVC. I have a requirement where I need to show a ReportViewer and for that I am using a classic ASP.NET page. The problem is when I am trying to redirect from the action I am getting following issue:
The IControllerFactory 'StructureMapControllerFactory' did not return a controller for the name 'Reports.aspx'.
I am using one webservice, which is for .NET platform, for address validation.Its running successfully on .NET (C#). However, I also want to use the same service from classic asp (legacy code) pages. Would appreciate if someone could give a clue how togo about it? Here are some ideas that I came up with and would appreciate if you could add to it
We are migrating an ASP Classic website over to ASP.Net. One of the big hurdles is the large amount of data stored in SessionState by the ASP Classic website.
I am looking for ways that session state can be shared between the two applications. I found the following link from microsoft MSDN that describes how to share session with a shared database. Unfortunately it uses the binary formatter to serialize into the database and I have recently had some bad experiences with said binary serialization.
how to share session state? or alternatives to the binary serialization?
That out of the way, here's my situation: We are looking to port our existing classic ASP application to .NET, but we're unsure of what language to use for the new app.
I personally would 'prefer' C#, as I'm more familiar and comfortable with that languages way of doing things, but, the original code is VBScript, so it would possibly be easier to port to VB.NET ... One possible situation I fear would be that, because the code is so similar between the two variants of VB, that we might end up getting stuck on something that is not similar between the two, even though it looks like it would work. A shift to a wholly different language might avoid that kind of situation.
Does anyone have any practical examples of this kind of situation? Insights to illuminate the issue with? Do the potential benefits of a complete paradigm shift outweigh the gains from a high degree of 'copy-and-paste-ability' ?
