.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

V1.1 to Beta 2 - Namespaces Not Recognized

Posted By:      Posted Date: August 24, 2010    Points: 0   Category :ASP.Net

We are attempting to test out a website written in VS2003/.Net 1.1 in VS2005 Beta 2/.Net 2.0.  Our main problem at this point is that certain classes are not being recognized when they are referenced in other files not in the same directory as the class file.


A Framework.cs file under \Applications is inherited by several other webpages. It resides under the namespace Company.WebSite.Applications.

Another class, SearchHistories, is in \Applications\CrackHistory directory. The namespace of SearchHistories class is Company.WebSite.Applications.CrackHistory. SearchHistories inherits Framework.  Under .NET1.1, there was no problem with this. However, in VS2003, a compile error states "The type or namespace name 'Framework' could not be found (are you missing a using directive or an assembly reference?) C:\WEB\Applications\CrackHistory\SearchHistories.aspx.cs".

The immediate solution is to copy the Framework.cs file from the Applications directory and copy it into the Applications\CrackHistory directory. Then the error goes away. What is up with that?

View Complete Post

More Related Resource Links

ASP.NET 4 and Visual Studio 2010 Web Development Beta 2 Overview

Many exciting changes for ASP.NET are coming in the .NET Framework version 4. This document gives an overview of many of the new features that are included in the Beta 2 release of the .NET Framework 4 and of Visual Studio 2010.

Visual Studio 2010 Beta 2

This is a big deal. This isn't ".NET 3.6" - there are a lot of improvements of .NET 4, and it's not just "pile on a bunch of features so you get overwhelmed." I've been working with and talking to many of the teams involved and even though it's a cheesy thing to say, this is a really customer-focused release.

ASP 4 - Whirlwind Tour around .NET 4 (and Visual Studio 2010) Beta 1

There's a lot of stuff that's new and added in .NET 4, but not in that "overwhelming-I-need-to-relearn-everything" way. More in that, "oh, this is way easier/simpler now" way. Like, moving data around with ADO.NET DataServices is easy, binding with client templates is easy, there's F# if you need it, the "dynamic" keyword if you need it, Silverlight's already installed, oh, and the parallel stuff will freak you out, but in a good way.

Service Station: Developing .NET Web Services with Beta 2


Version 2. 0 of the Microsoft® . NET Framework makes numerous improvements at various levels in the Web services protocol stack. In addition, better tool support and an increased focus on interoperability make your life easier.

Aaron Skonnard

MSDN Magazine April 2005

Security: Protect Private Data with the Cryptography Namespaces of the .NET Framework


The .NET Framework includes a set of cryptographic services that extend the services provided by Windows through the Crypto API. In this article, the author explores the System.Security.Cryptography namespace and the programming model used to apply cryptographic transformations. He discusses reasons why cryptography is easier in .NET than it was before, including the easy programmatic acccess developers have to the cryptography APIs and the difference between symmetric and asymmetric algorithms. Along the way, a brief discussion of the most widely used algorithms, including RSA, DSA, Rijndael, SHA, and other hash algorithms, is provided.

Dan Fox

MSDN Magazine June 2002

.NET Migration Case Study: Using ASP.NET to Build the beta.visualstudio.net Web Site


When the Web site used to collect customer feedback about the Visual Studio .NET beta needed an update, the Visual Studio team saw a good opportunity to implement, deploy, and showcase a real-world site using .NET technologies. This article covers the migration of the Web site, beta.visualstudio.net, from components written in Visual Basic 6.0 and ASP hosted on Microsoft Internet Information Services (IIS) 5.0 to ASP.NET and the .NET Framework. The choices of technologies to be incorporated, along with issues such as validation, security, and authentication, are all discussed. Both existing components and the new components written in JScript and ASP.NET that were used to migrate the site are also explained.

Jay Schmelzer

MSDN Magazine September 2001

Microsoft SharePoint Designer 2010 Beta (32-bit) - Now Available!

Using SharePoint 2010 Designer, advanced users and developers alike can rapidly create SharePoint solutions in response to business needs. In addition, developers can use SharePoint Designer 2010 to get a quick start on SharePoint development projects.

Microsoft SharePoint Designer 2010 Beta (64-bit) - Now Available!

Using SharePoint 2010 Designer, advanced users and developers alike can rapidly create SharePoint solutions in response to business needs. In addition, developers can use SharePoint Designer 2010 to get a quick start on SharePoint development projects.

Microsoft SharePoint Foundation 2010 Beta - Now Available!

This download contains an installable version of SharePoint Foundation 2010 Beta that can be used to assess and test the new functionality in this release. SharePoint Foundation 2010 is the new version of Windows SharePoint Services.

Microsoft SharePoint Server 2010 Beta - Now Available!

SharePoint 2010 provides a robust development platform to rapidly build solutions using familiar tools like Visual Studio 2010 and SharePoint Designer 2010. Developers gain access to a rich set of out-of-the-box features such as Business Connectivity Services for read/write integration between application data, the web and Office 2010 client.

WPF+ VS2010: Design mode error "The URI prefix is not recognized"?

our application uses VS2008 and WPF. To apply the styles in the design mode, we have used the "BlendMergedDictionary" class (see the following link) http://stackoverflow.com/questions/995101/how-do-i-get-wysiwyg-design-in-blend-vs-without-merged-resourcedictionary-in-ever It works very well in VS2008 IDE. Now we plan to move our application to VS2010. In VS2010 Design mode (click on ~.xaml design), we get error message:  "The URI prefix is not recognized."    at System.Net.WebRequest.Create(Uri requestUri, Boolean userUriBase)    at System.Net.WebRequest.Create(Uri requestUri)    at MS.Internal.WpfWebRequestHelper.CreateRequest(Uri uri)    at System.Windows.ResourceDictionary.set_Source(Uri value) the styles does not apply at the design time. It works fine in runtime. The following are the code: public class BlendMergedDictionary : ResourceDictionary { /// <summary> /// This class the purpose is allow we reference the "themes" and "styles" in resource dictionaries in separated assemblies /// by using StaticResource. The big problem using StaticResource is that it will complaints at design time can not find the resources /// So we use this class in xaml file, if it is design time, it will load the resource dictionaries in. /// If it is not in design time, it will use the reso

Removing Xml Namespaces from XmlSerialization

I am currently using Xml Serialization to serialize my classes in Visual Studio 2010, but I have been unable to remove the default namespaces that get attached to my document. These two elements get attached to the root of my document each time. xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" When I specify my XmlRoot attribute on my class, I have tried both methods: [XmlRoot("requestor", Namespace="")] as well as <pre lang="x-c#">[XmlRoot("requestor")] Both of these methods have continued to result in the namespace being appended to my XmlDocument. This is currently the method I have been calling for my Xml Serialization: <pre lang="x-c#">/// <summary> /// Performs XmlSerialization of a particular object/class /// using the .Net Xml Serializer /// </summary> /// <param name="objForSerialization">object or class instance to be serialized</param> /// <returns>string containing the serialized object in Xml Document format</returns> public static string XmlSerialize(object objForSerialization) { string strSerialized = string.Empty; using (MemoryStream memoryStream = new MemoryStream()) { XmlSerializer serializer = new XmlSerializer(objFo


Hi,A rather basic question coming up, but it does say no question too simple.I am coding for the first time in .net and looking at namespaces and classes.  If had a look on the web but I'm still not totally clear on right approach to structuring them.For instance:If I have 2 classes, called EmailTemplate and EmailSender, how would I structure this?  Do I do this...in the first class namespace Email { class EmailSender { } } then in the second class namespace Email { class EmailTemplate { } } or am I getting it totally wrong?Any advice would be apprceciatedJohn
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend