Thread: Visual Studio 2010

I am using the Visual Studio 2010 Beta 2 and my site no longer compiles
these lines of code in XmlPackage2.cs under core are causing the issue

C#/VB.NET Code:

XsltObjects.ExtensionConfiguration objExtConfig = XsltObjects.ExtensionConfiguration.GetExtensionConfiguration("xsltobjects");
                if (objExtConfig != null)
                {
                    Object userExtObj;
                    foreach (XsltObjects.Extension ext in objExtConfig.Extensions.Values)
                    {
                        userExtObj = ExtensionObjects.CreateExtension(ext.Type, m_ThisCustomer, m_SkinID, null);
                        m_TransformArgumentList.AddExtensionObject(ext.Attributes["namespace"], userExtObj);
                    }
                } 


It says namespace XsltObjects does not exsist (and it doesn't) however what can I do to fix this? I have tried to just comment out these lines of code however then the site doesn't work.

Please help.

I've done some work with beta 1 and never ran into any issues like this. I'm grabbing a copy of beta 2 now and will let you know my findings. You may want to just double check that the reference in the core project to XsltObjects still exists and that XmlPackage2 correctly uses it.

I get the same error with VS 2010 Beta 2 here locally. After sifting through different articles, I found one on Microsoft Connect describing this issue exactly where they say they've already resolved this issue for the final 2010 VS release however it didn't make it into the VS 2010 Beta 2

Hmmmm....I don't buy it. Not sure why but the conversion process isn't picking it up either. Will have to dig deeper....

Ok...still not sure why, but to resolve you can take the following steps.

1. Copy the XSLTObjects folder to somewhere on your desktop
2. Delete the XSLTObjects folder from your build and remove from the solution in VS
3. Add a new project called XSLTObjects to the solution in VS
4. Create a new class called Extension.cs in the XSLTObjects project
5. Copy/paste all code from Extension.cs on your desktop to the Extension.cs file in your project that you just created.
6. Save the new Extension.cs class in the XSLTObjects project
7. Repeat steps 4, 5, and 6 for both the ExtensionConfiguration.cs class and the ExtensionConfigurationHandler.cs class
8. Add a reference to the .NET assembly System.Web in the XSLTObjects project
9. Re-add the references to the XSLTObject project in the other projects that need it
10. Rebuild the solution

OK, I'll give it a go.

Thanks for all your help.
I was worried there would be no fix. Thanks again for all your help.
Shame the beta 2 does that, its looking really good.

Just done it, worked perfectly. Build is fine now.

Thanks for all your help.

Seems now my checkout no longer works with the new dll.

I'll take a look, but please tell me that you aren't using these to push to your live site?!?! Just as you shouldn't try and go live with a beta version of our software, you shouldn't use other beta software to run it.

I originally was using it for the localhost version of the site for testing and doing changes that do not require core changes. However I soon came across the need to change some core files and without thinking set about doing them.

Our live site is fine for now, I simply backed up the dll before every upload so it was easy to fix. However I cant use older versions of VS now because they have been upgraded by VS10.

I am getting the same error with the release version of 2010 and ML 9.0.

2010 has lots of new features that help in development and I would like to use it. Any solution for this?

George's suggestion on page 1 worked for me. Looking at the conversion log (converting from vs2008-2010) each of the classes in the XSLTObjects project failed.. which is probably what the issue was.

Luckily there's only 3 of them... a shortcut is to move the folder somewhere else on your hd, remove the project from the solution, create new project with same name, copy the cs files to the new project folder, and then include in project and rebuild.