This project is read-only.

ambiguous error ""Threating" is ambiguous, imported from other namespaces or types 'GeoFramework,System'."

Feb 26, 2012 at 8:31 AM

hi, i am facing with the ambiguous problem. and i don't know how to solve it. kindly advice.

i try to search the solution for this at http://msdn.microsoft.com/en-us/library/aa479312.aspx , it provide me below solution:

 

Issue 22: Ambiguous references and naming conflicts

The .NET Framework 2.0 adds a host of new namespaces and classes. Several of these are likely to cause clashes with ASP.NET 1.x applications. For example, the new personalization features introduce classes with the names of Profile, Membership, and MembershipUser. The Profile name, in particular, is fairly commonly used by developers who want to keep track of user information. Therefore if you have a Profile class in your application, and you try to use any of the new personalization features, you may encounter compiler warnings about ambiguous class references.

How to fix

Planning ahead for naming conflicts can be rather difficult. You will want to take a quick look through the new ASP.NET classes. If you see any names that might conflict with what you have in your application, you might consider using explicit naming. For example, use System.Web.Security.Membership instead of importing/using System.Web.Security and then using the Membership class.

 

I not really understand the way to solve it. isn't i need to change the namespace  "Threating" in GeoFramework.PocketPC reference to another name to avoid ambiguous error?

May i know how to edit a refference (.dll file)? 

kindly advice. thanks in advance. 

Feb 26, 2012 at 2:07 PM
.NET 2.0 can't do this

On Sun, Feb 26, 2012 at 3:32 PM, cheekangteh <notifications@codeplex.com> wrote:

From: cheekangteh

hi, i am facing with the ambiguous problem. and i don't know how to solve it. kindly advice.

i try to search the solution for this at http://msdn.microsoft.com/en-us/library/aa479312.aspx , it provide me below solution:

Issue 22: Ambiguous references and naming conflicts

The .NET Framework 2.0 adds a host of new namespaces and classes. Several of these are likely to cause clashes with ASP.NET 1.x applications. For example, the new personalization features introduce classes with the names of Profile, Membership, and MembershipUser. The Profile name, in particular, is fairly commonly used by developers who want to keep track of user information. Therefore if you have a Profile class in your application, and you try to use any of the new personalization features, you may encounter compiler warnings about ambiguous class references.

How to fix

Planning ahead for naming conflicts can be rather difficult. You will want to take a quick look through the new ASP.NET classes. If you see any names that might conflict with what you have in your application, you might consider using explicit naming. For example, use System.Web.Security.Membership instead of importing/using System.Web.Security and then using the Membership class.

I not really understand the way to solve it. isn't i need to change the namespace "Threating" in GeoFramework.PocketPC reference to another name to avoid ambiguous error?

May i know how to edit a refference (.dll file)?

kindly advice. thanks in advance.

Read the full discussion online.

To add a post to this discussion, reply to this email (DotSpatial@discussions.codeplex.com)

To start a new discussion for this project, email DotSpatial@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com




--
-----------------------------------------------------------------------------------------
Nguyen Viet Cong
- TTM k52 _ BKHN
Mobile : 09 4488 6488
Tel : 0210 3 912 331
E.mail : CongNV@gmail.com
Skype : Nguyen.viet.cong.88
Yahoo : Linhhoncuaquy_MU


Feb 27, 2012 at 6:13 PM

I'm not sure if namespace aliasing would help you. (I couldn't find any reference to Threating.) Here's an example:

 

using GDI = System.Drawing;

namespace MyNamespace
{
  public class MyWindow : Window
  {
    public Point SomePoint { get; set; }
    public GDI.Graphics SomeGraphics { get; set; }
    public GDI.Image SomeImage { get; set; }
  }
}