No Compiler Directives in VS.NET 2005 Web Projects

Posted by: Rick Strahls WebLog, on 25 Dec 2005 | View original

Here’s another side effect of the project less ASP.NET projects in Visual Studio 2005: You loose the ability to use global compiler directives. I have a couple of projects that compile to different targets – one within a framework one just as a standalone and I’m using Compiler directives defined at the project level to cause a handful of changes in these ASP.NET projects.   This is a bummer… I haven’t been able to figure out a way to get around this short of hunting...

Advertisement

Similar Posts

  • Windows Workflow Foundation (WF) more
  • Sharepoint 2007 & ASP.NET 2.0 WebParts more
  • This blog is now closed. Please update your links. more
  • Blogging from Tech Ed 2006 - Stefan Shakow on ASP.NET - level 400 more
  • Calling web services hosted outside of your application with Atlas more
  • Common Gotcha: Slow VS 2005 Web Site Build Performance Because of Dueling Assembly References more
  • Implementing 3D Tic-Tac-Toe game in Visual Basic more
  • Getting LINQ to work in your new or Exisitng non-LINQ setup project more
  • Run Cassini as Root Web within Visual Studio more
  • Web Service Proxy Objects and COM Interop Problems more

News Categories

.NET | ADO.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Community Server | dasBlog | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD