The Artima Developer Community
Sponsored Link

.NET Buzz Forum
Whidbey & Longhorn Project Name Restrictions

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Jason Nadal

Posts: 184
Nickname: jnadal
Registered: Dec, 2003

Jason Nadal is an asp.net developer, dabbling in winforms from time to time.
Whidbey & Longhorn Project Name Restrictions Posted: Mar 20, 2004 3:46 PM
Reply to this message Reply

This post originated from an RSS feed registered with .NET Buzz by Jason Nadal.
Original Post: Whidbey & Longhorn Project Name Restrictions
Feed Title: Jason Nadal
Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/jnadal/Rss.aspx
Feed Description: Restless C#ding
Latest .NET Buzz Posts
Latest .NET Buzz Posts by Jason Nadal
Latest Posts From Jason Nadal

Advertisement

This is just a reminder that strange things can happen when you try to name a project with an existing class in the .NET framework.  For example, for creating a new sample test project, I usually give it some sort of simple descriptor and put it in my HD's example code folder.

I was playing around with some very simple animation, and wanted to keep around a sample of animations based on paths, so I name my project PathAnimation, put some code in, attempt to compile, and get turned down because the PathAnimation class already exists in the 1.2/2.0 framework... whoops!

Read: Whidbey & Longhorn Project Name Restrictions

Topic: DevDays Denver is Over Previous Topic   Next Topic Topic: What I Have Been Doing the Last 10 Months - MobileGuardian

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use