Avatar of ewinche

asked on 

Running ASP.Net on Vista Home Premium

OK I surrender. I'm trying to develop asp.net applications on my laptop through localhost, operating  with Vista Home Premium and Textpad as my editor.
I have searched the web, have moved on through various errors.
First was: "An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode."

Then after altering web.config the error became: Could not load type 'AspNetReadOnlyXmlMembershipProvider'

And finally after attempting to expand all permissions to full, I get this error
      Could not load type 'AspNetReadOnlyXmlMembershipProvider'.
This is the current problem.
I have converted the app folder to a web app folder.
My web.config, I believe, is a mess as I am unfamiliar with the various settings. I'm looking for a no frills web.config that will allow me to run localhost asp.net pages.

Thanks for your help.

Avatar of undefined
Last Comment
Avatar of ewinche


The answer for me, to get locally developed asp.net programs to run under Vista Home Premium, after five months of trying, is as follows:
My development environment is:
      I use Textpad as my editor, not Visual Studio, so I had been trying to run a simple       login2008.aspx program with little luck for many months.
The first error that I got when running was:
"An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode."

I had no idea what "Integrated managed pipeline mode" was so I searched about to find answers. The error message itself contained the solution toward the bottom of the page (the second bulleted item)under the heading:
Things you can try: 
"      If the application supports it, disable client impersonation.
"      If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false.

After some thought I decided that I needed a correct web.config file to run asp.net programs on my Home Premium machine. The various web.config files I had seen on web posts were frightening in their complexity. Nevertheless I found one that seemed to talk about "pipeline mode" so I copied it and used it, placing it in wwwroot.
I thought it was a good bet because it contained a line as follows:
Which seemed to respond to the bullet above which wanted the system.webServer/validation@validateIntegratedModeConfiguration set to false
Though it was not the exact wording I thought it close enough. I would rather have seen:
in the  section of the web.config file include a validation tag as follows:

So I borrowed this web.config file and tried again. Finally I gathered that there were many other things in this web.config file that produced errors and while the Integrated managed pipeline mode error went away I now had another error, namely
Could not load type 'AspNetReadOnlyXmlMembershipProvider'.
That proved just as daunting. To condense the process Ill say that I finally settled on a bare bones web.config as follows:
<?xml version="1.0"?>


This was fine - is fine, but I still had to eliminate various other files related to my many attempts to get this thing up and running. That includes files associated with my failed attempts to use special asp login controls and a membership/role provider (?) linked to files in the APP_DATA and APP_CODE folders.  I had a line in a former web.config in the  section that said:

This I believe led to the "Could not load type 'AspNetReadOnlyXmlMembershipProvider'' error, so it and many other line are not in my current working web.config.

I might use those wonderful, powerful tools at some later time, and expand my web.config accordingly,  but for now I just wanted to see my pages displayed in the web browser with the localhost (or url as follows -  http://localhost/programname.aspx.
 So now my page displayed in the browser, but when I moved on to a page that updated the database I got the following error: "Operation must be an updatable query. 

I was familiar with this error from asp 1.0 and XP days so I felt hopeful. To fix this do as follows:
    Right click on the folder that contains the database, select Properties and then click Sharing tab.  
    Next click the Share button which brings up the File Sharing window.
    Click the Share button at the bottom here also (don't bother with the text box or the message at top).
    Next right click again on the database folder, click Properties then Security tab.
    Select the "IIS_ISUSRS  group and click Edit so you can give full control (click the Full Control
     checkbox) to that group.

This will remove the updatable query error.

That did it for me. I can finally develop asp programs on my Vista Home Premium laptop. hope this helps someone
Avatar of EE_AutoDeleter

Blurred text
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial

The successor to Active Server Pages, ASP.NET websites utilize the .NET framework to produce dynamic, data and content-driven web applications and services. ASP.NET code can be written using any .NET supported language. As of 2009, ASP.NET can also apply the Model-View-Controller (MVC) pattern to web applications

Top Experts
Get a personalized solution from industry experts
Ask the experts
Read over 600 more reviews


IBM logoIntel logoMicrosoft logoUbisoft logoSAP logo
Qualcomm logoCitrix Systems logoWorkday logoErnst & Young logo
High performer badgeUsers love us badge
LinkedIn logoFacebook logoX logoInstagram logoTikTok logoYouTube logo