We had a working website built on framework 2.0 with membership. After we converted it to framework 3.5 using the Visual Studio automated conversion mechanism by opening it in Visual Studio 2008 and following the prompts, the membership system is now broken. Dammit, all we wanted was some newer AJAX.
The rest of the site appears to be functioning fine, but when it comes to logging in or managing security on the site, it fails.
So the errors we receive when trying to manage security via the built-in admin pages, seem pseudorandom; everything from 'user cannot log in to database' to 'this file is being used by another process' to 'there's a problem with your datastore'.
What sort of datastore are you using? SQL Express MDF file in your App_Data folder? External SQL Server? Did you change anything in web.config?
So far as I know, there were no real changes to Membership features between 2.0 and 3.5... I think you've got something else going on.
You can rollback your changes and test the old system, right?
Thanks Bryan for your response, but this turned out to be a complete disaster and it's something I would NEVER do again. I just came back to say this to anyone who tries it in the future: "You just made a very bad mistake."
Yes, we ended up rolling back, if that's what you call it when you have to re-get everything from SourceSafe to a completely new directory because there is no auto-rollback feature with the framework conversion, only a backup folder that has been screwed with and dumped into another folder and will never work again because all references are now broken and the web.config has a bunch of illegal entries, and the IIS metabase ended up corrupted, and intermittent database locking caused permissions to be wiped, and around 15 or 20 other problems.... there is no solution to this issue. Not really.
Of course I've personally updated many projects using the Visual Studio upgrade system. But never a website, and never one this complex. And now, never again. :-)
Related
I´m trying to start a project I pulled from a colleague. No errors, no visible issue in the project.
The project starts without problems, but immediately force me to login to Umbraco. When I enter credentials for the Admin I am returned to a view that is forcing me to upgrade Umbraco version, something I do not want to do since the project is live on the Umbraco I´m currently on.
I have worked with Umbraco before on several project and never experienced this issue.
The project is running fine on my colleagues computer, connected to the same umbraco database. He has no changes that are not committed to the repository I´m pulling the project from.
Any ideas what might be causing this situation?
Umbraco v6.2.6 (Assembly version: 1.0.5906.18846)
Thanks and best regards, Martin
Check that the version of Umbraco in the core DLLs matches the one that's in the "umbracoConfigurationStatus" appSettings key in your web.config file. If they're different, it'll try and get you to upgrade. Compare against your colleagues machine as well to see if there's a difference between what's on his machine and yours.
You get the upgrade message when Umbraco detects a mismatch between the version it's running and what the web.config file says the site is running.
I was hoping to get some people's expertise as I'm currently outside my main domain. I'm currently working for a client that has an old system written in VB6 COM Objects. They use these to do basic Database interaction. These COM Objects are used in a Classic ASP website.
I've been tasked with getting the site up, running and in a build-able environment (Windows 8.1 is what they want to use).
I've been working through all the blockers associated with this and I believe I have it in a running state (as in I've configured IIS and been able to run the website, log in and click around and so far nothing has crashed).
I can make changes to the code in Visual Studio 6 Enterprise and those changes are working so I'm confident I've got that about 90% of the way there.
I've now got 2 problems both somewhat related:
Problem 1:
Problem 1 is now debugging, both the ASP & the VB code.
I can put a break point in the VB code and 'Step-Into' it (to attach) and then run the site and the code that runs in the global.asa file gets run and hits that breakpoint no worries, can step through as I would expect.
The problem then comes when I go to 'login' to the system. I use the same user/password that works if I'm not 'attached' the system crashes with a "An unhandled exception ('Error in loading DLL') occurred in w3wp.exe [3284]." - If i try to load up a debugger from this Visual Studio 6 is not an option in the list. If I then detach and I can do everything as before.
Does anyone know what could be causing this? Or have another way to be able to debug/step through this?
Problem 2:
They had previously been 'running' the website through Visual InterDev 6.0 - they could add breakpoints to the Classic ASP code and be able to step through then into the VB components.
The problem is that although I can install InterDev on my machine, I can't actually set it up. It appears to need FrontPage Server Extensions which although they can be 'installed' on IIS 8.5 they don't seem to be officially supported by Microsoft. So I've managed to install it without any issues but it doesn't seem to be configured in the same way that InterDev needs it to be able to setup a solution file/run from it.
My Question is this: Has anyone been able to configure FrontPage Server Extensions in a way that InterDev works?
OR is there any other tools I could use to 'run' a Classic ASP site that would allow me to debug it properly.
Let me know if you need any more information.
Thanks in Advance,
Michael
I think you actually don´t need Interdev in order to debug the classic ASP code. Just create a blank solution in Visual Studio and add all the classic ASP files from the virtual directory (editor and debugging capabilities for classic ASP files are still supported, even in the latest version of Visual Studio).
I assume you run the web application in your local IIS... once you have the solution, open the script of interest, put some breakpoints and than attach the Visual Studio debugger to the web server´s worker process (which should be w3wp.exe). Maybe you need to manually select the Script code type (automatic code type detection might not work).
I need to get a classic asp project up and running but do not have IIS installed on my computer. Is there away to run the project without it? I currently have visual studio 2005
thanks
jason
There is something called Abyss Web Server - I've never used it myself so can't vouch for it but from its description and features it looks promising.
If money is the issue, Microsoft came up with IIS Express some while ago which is free to download and use and from this question looks like it's supporting classic ASP as well.
I have no idea whether you can even get hold of this software anymore but Sun used to maintain a project called Sun One Active Server Pages (aka ChilliSoft ASP) which allowed you to run ASP sites without IIS
There may be some weird and wacky solutions (like a "compiler" to ASP.NET etc) out there, however I really doubt any such thing would be worth it.
I would make more sense to pursue the answer to this question: "Why don't you install IIS on your machine?".
godaddy.
$5/month until you cancel it.
instant gratification
call them now, and then start building your asp app a few hours later.
why hassle with the path you are inclining towards?
I've asked a question about changing the version of .Net sites in the IIS. If it affects classic asp sites etc (See Does asp.net setting affect classic asp (IIS 6 settings))
And that seems fine. So my follow-up question is, will running this command get me fired? What it does is changing the default value (and all existing?) of the .net version to 2.0.
This wont affect any of the .net sites since they're allready versioned to 2.0.
The classic asp pages needs to get its app pools updated so its functionoal with 2.0 but may I run into any other troubles?
I've tried doing this on a test environment and no sites whet down during the installation period (from the command) but I did not have any classic asp sites or any .net sites running though (which I should test, come to think about it) but may something else break?
Is this command doing anything else? We have some very large sites running and we cannot have downtime periods so I need to be 100% sure that this command is safe. Since all sites go down everytime we change a new sites .net version number we need to get this fix live asap.
Any good ideas?
This should not cause any side affect as it relates to what the IIS does with .NET pages (e.g. aspx extensions).
Since the classic asp pages are not handled by the .NET extensions in the IIS I can see no reason to worry.
EDIT:
According to MSDN you can use an option
-norestart - inhibits the restart of the World Wide Web Publishing Service after installing or updating ASP.NET script maps. If you do not use this option, all application pools are recycled.
so you can see from that application pools will be recycled.
long time since I asked, but Dror, thanks for your edit. I'll be sure to try it.
I actually found a solution to this problem some months ago.
You can export a sites configuration, and you get a XML file, edit this file and set the site name etc to something (like dev1). Then you import this and you got yourself a new site with .net pre-configured. Just make sure you change the name and other things that cannot be the same as another site (like host things, cant remember exactly what parameters there were) because that would cause a problem I guess.
Happy iising
I have an ASP.Net 2.0 web site, using the DotNetNuke framework (4.09), and it will not compile, but when I hit the site in a browser, it works. Even the parts that don't compile will work. How is IIS able to compile and run this site, when Visual Studio can't? Everything is the same in both places... I copied the entire web site from the remote server on to my local machine, then I set it up in IIS the same way. On my local machine, Visual Studio can't compile the site, but it still runs. How can this be possible?
The specific errors are not important, as there are 189 of them, from every possible part of the site. I'm not trying to fix the errors... what I want to know is how it's possible for the web server to run the site, regardless of the errors. Please pay attention to what I have written - everything is exactly the same in both places. There are no missing DLLs, no different configurations, nothing on the machine itself... remember, the site runs fine on my local machine.
Is this a web site or a web application? If it's a web application, you're probably still running off the last successfully built bits in the bin.
The site is using old dlls, or possibly you have references missing in your local version that the server has just fine.
As Mitchel said, we need to see the error before we can really answer your question.
To give you an answer on this we would need to know what the errors are.
Your local machine cached the 'working' copy and is using that maybe?
The site was compiled successfully at one point as it works on the remote server. Thus, copying it to your local machine and hitting the local site will also work. However, there can be several reason why you can't re-compile it on your local machine including; missing references, web.config entries, third party control licensing, etc..
I realize you are not trying to correct the 189 errors, but there are clues, if not answers, in the error listing that will get you moving in the right direction.