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 have an old website running fine in Classic ASP with large customer base registered onto the site. The current site allows users to have their own user name(unique) registered against an ID assigned to them. They can change the User name later as well provided it is still Unique in the database(Database is SQLServer2005).
The Problem: Now i want to move the website to .NET and want to use the .NET Membership. I know how to create the database structure in SQL Server through aspnet_regsql script but my problem is how should i import the existing username and passwords as the password stored in MembershipDB is Hashed (salt). Also i might want to allow admins to impersonate as users later.
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?
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.
I have a website that's in Classic ASP on a hosted server. I'd like to be able to create some "virtual" pages so I can specify google-friendly URLs that translate to ASPs [URL] this_is_the_help_page instead of [URL]admin/helpsubsystem/help.aspx?current_user etc As the server also supports ASP.NET - could I use an HTTP Handler to intercept these calls and do any necessary translations?
We have recently migrated one of our legacy websites (classic ASP) to ASP.Net 4.0. I have already created a RegisterRoutes() in Global.asax (as per [URL]). I am concerned about SEO rankings and link breakages with external sites linking to old site.
Ideally, I will like to: Load all the routes from an XML file within RegisterRoutes() --> As there are 100's of pages with no naming convention followed. We have already created mappings within an excel spread sheet which can easily be exported to XML.Action Permanent redirects from within RegisterRoutes() --> to avoid having landing page(s) performing Redirects like Response.RedirectPermanent() and Response.RedirectToRoutePermanent. Has anyone run into a similar situation? Is there a better way of handling this situation?
I'm working on a website with legacy Classic ASP pages (being converted to ASP.NET on an as needed basis) and new ASP.NET pages. Use of IIS 7 Integrated Pipeline has been very helpful with our configuration. For example, we were able to get forms authentication working auto-magically with the classic ASP pages simply by configuring the appropriate sections of the web.config file (i.e. no changes were required to the Classic ASP pages, for more info see this).
A colleague of mine believes that custom error pages, as specified in the web.config <customErrors> section, should also be auto-magically applied to the classic ASP pages, but for our website it only works for the ASP.NET pages. Nor have I been able to find any information describing the capability of applying custom error pages to Classic ASP with the IIS 7 integrated pipeline. Is it possible to apply custom error pages to Classic ASP pages per a web.config for an website running under IIS7 with integrated pipeline? If so, how?
everything .net works fine, but when i try to run a .asp file i get this error: Server Error in '/xx' Application. This type of page is not served. Description: The type of page you have requested is not served because it has been explicitly forbidden. The extension '.asp' may be incorrect. Please review the URL below and make sure that it is spelled correctly. Requested URL: /index.asp Version Information: Microsoft .NET Framework Version:2.0.50727.3607; ASP.NET Version:2.0.50727.3082 is there something i need to enable?
I'm getting close to finishing a public-facing ASP.Net app and I'm starting to weigh deployment options. I'm an ASP.Net/SQLServer veteran but noob when it comes to Azure. I'm wondering how others have felt about the learning curve to effectively migrate a local dev ASP.Net/SQLServer apps into Azure cloud. More specifically:How steep is the learning curve towards understanding administration and programming concepts, and do you think it's worth the investment?What is Microsoft's support like if I have catastrophic problems from my cloud infrastructure and my live site is down? My expectation is a large price tag for a not-so-urgent SLA.Will my non-Azure ASP.Net app require significant modification and/or coupling to run in the Azure environment?
We already have our vb.net project in asp.net1.1 framework now we are changing the framework to asp.net4.0.But we are facing more warnings like unused local variables and function need return statement.it exceeding maximum warnings because of these kind of issues.Is there any tool to remove unused local variables.
I have upgraded my web site from 2.0 to 3.5 using VS2008 (loaded the project and selected 'yes' to the upgrade prompt), then deployed to the Live server. On the test system the website runs fine, on the Live, it fails with 'Assembly binding' (System.Core, System.Web.Extensions, and more) errors. When I commented out all the failed assemblies (just to see what happens) I got the error: 'csc.exe' cannot be found. Can anyone tell me what is wrong? 1. Is my upgrade method wrong? 2. Is there another way to upgrade? 3. How can I tell why the assemblies fail to bind?
After migrating my app to .NET 4 it's not starting. When i'm trying to load it in browser it endlessly loading it and nothing else happening. There is no errors or timeouts, just loading.
I am tryin to rebuild a website designed in asp.net.But,being an informative site it has a lot of content in it which i dnt want to input to the database manually.can ne1 help me out with any drupal module to migrate the asp.net data in sql server to mysql db in form of drupal architecture??say for example a page in asp.net is displaying data from a form.Can i migrate it in form of cck and get the page data as nodes table.
I know very little, and even less about .dll's. I have a fairly simple albeit old, application that references a .dll that seems to do the logic for connecting to an access backend. I don't have the source code for the dll, but I don't see any code anywhere elese to sigify the dataconnections etc. When I move the application from an old IIS6 server .net 1.0, over to a newer IIS7 server with .net 2.0osmething, I errors out (see below). When I remove the reference to the dll, the login pages comes up okay but I just can't login. So, something is up with my DLL. What do I need to do?
Error Information: Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission contact your system administrator or change the application's trust level in the configuration file.
Exception Details: System.Security.SecurityException: Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'failed. Source Error:
New functional requirements stipulate that what was once a one to many relationship is now a many to many relationship. The relationship comprises a simple lookup table
How does one manage the migration of data from the old structure to the new???
I have the following script which will move the data from/to the right tables:
[Code]....
What i'm wondering is, once i have run the script to copy the data across, do people recommend that the LegacyTable.LookUpPK_ID field be deleted permanently?
we are currently investigating a migration of an application that doesn't meet company standards. The application is built using VB6 and Shape SQL/Access. The application has about 120 reports by storing Shape SQL strings in a database which the user can modify using a wizard. Shape sql is not allowed at this company. We have investigated plain SQL, Linq, Entity Framework as alternatives... but all result in more complex solutions.
Update: Shape SQL is an ADO command to get hierarchical datasets, for further info:
Recently I moved my developing environment (Visual Studio 2005) on Windows 7. I followed the steps for migrating from IIS6 to IIS7, but when I try to start debug my web project I receive the error message:
"Unable to start debugging on web server. Debugging failed because integrated Windows authentication is not enabled."
We have a few settings in our web application that can be user configured. As IIS exposes helpers for configuring "Connection Strings" and "Application Settings" we decided to take use this method of configuration.
Unfortunately this works by editing the Web.config file deployed in the web application. This means that a simple upgrade process of copying over the files from a newer web application release resets all configuration settings to the default.
Possible options:
When upgrading the webapp, backup the Web.config and restore it afterwards. This is not elegant and if the latest webapp defines new default-valued properties in the Web.config then this will break Write some admin-only configuration pages on the site and store the values in the DB. This puts the control back in our hands, but it will take work to write this and obviously has bootstrapping problems with connection strings.
I was working on migrating MVC1 app to MVC2 today and i have come across a problem while changing the ValidationMessage to ValidationMessageFor implementation.