博客园  :: 首页  :: 新随笔  :: 联系 :: 订阅 订阅  :: 管理

I'm using visual studio 2005 beta2 to open the Microsoft Enterprise
Library June 2005. When I open the solution as follow "C:\Program
Files\Microsoft Enterprise Library June
2005\QuickStarts\ExceptionHandling\CS\ExceptionHandlingWithLoggingQuickS
tart.sln", the IDE throw an exception
================================
"There is an error in xml document(1,1747)"
It stop at the file ConfigurationSettingsLoader.cs
Line 72
================================

After I fix the problem I indicate above,I find a new error! I'm dying soon,my god!

After some trials and tribulations, I have finally the initial projects created by CodeSmith to compile using the VS 2005 setting.  I am using the latest version (as of yesterday) of the code from CVS.  I am using the CVS versions of NetTiers.Configuration.2005.dll and NetTiers.Configuration.Design.2005.dll and NOT the versions from Rational Path.
 
After getting it to compile, I added a WinForms project, configured it using the EntLib configuration tool and everything worked perfectly. 
 
Next, I tried creating a new web site project.  I added a web.config to the site, and configured it using the EntLib Configuration tool.  Once again, everything compiled.  However, when I opened up the web.config in VS2005B2, I get the following error:
 
Warning 59 The element 'configuration' in namespace 'http://schemas.microsoft.com/.NetConfiguration/v2.0' has invalid child element 'enterpriselibrary.configurationSettings' in namespace 'http://www.microsoft.com/practices/enterpriselibrary/08-31-2004/configuration'. Expected any element in namespace 'http://schemas.microsoft.com/.NetConfiguration/v2.0'. C:\Applib\DotNet2\ArtPackCS\WebSite1\Web.Config 43 4 C:\...\WebSite1\
When I try and run the project, I get following error as a pop-up within VS:
 
Error parsing application configuration file at line 45. Type
'{http://wwww.microsoft.com/practives/enterpriselibrary/08-31-2004/configuration}ReadOnlyConfigurationSectionData' is not found in Schema.
 
Please correct before proceeding.
(You might rename the current web.config and add a new one.)
 
Strange error...

Thanks!

Kent