My web application requires .NET 4.0, but we have been testing locally using .NET 4.0 on IIS 5.5. I migrated the application at DiscountASP.NET to IIS 7.0 and have been able to successfully work through the configuration problems. Until now. I finally have the webform running, but I am getting the error that I get when a database is inaccessible. My application communicates with the database through a code library called: WebBusiness.Data.dll. This code library contains a series of .xsd files that communicate with the database through table adaptors. Why would my database not work in IIS 7. The connection strings are registered in the Web.Config file. The WebBusiness.Data.dll loads the connection string with ConfigurationManager.ConnectionStrings["CNX"].toString(). It works fine locally with our production database, and these table adaptors have worked fine for years. What could be causing the issue. I am at a loss for where to even look next.
The error is Index cannot equal -1... It is becuase the dataview that typically gets the page data is empty. Most likely this is a db connection, connection string, IIS 7 connection rule issue that we are unaware of... because it works in other environments.
I have beend debugging this issue nonstop for two days now and what I have found is that the application on IIS 7.0 is not loading or reading from teh .dll libraries that are located in the bin. I am not sure why. These libraries are refrenced in the project and work great in IIS 5.0 running .NET 4.0... Why whould a move to IIS 7.0 stop these code libraries that are registered as controls in the web.config from running approprately?
I was able to get the application running locally on a Windows 2007 PC running IIS 7 by switching the application pool to .NET 4.0 classic. My .dll files would not run in .NET 4.0 integrated, but they run in .NET 4.0 classic.
You can switch between integrated and classic mode for your account here in the IIS tools section of Control Panel.
