TPN :: The Microsoft Developer Show http://msdev.thepodcastnetwork.com Your Passion...Your Potential Tue, 24 Jun 2008 20:30:16 +0000 http://wordpress.org/?v=2.0 en The Podcast Network 2003-2006 cameronreilly@gmail.com (The Podcast Network) cameronreilly@gmail.com Technology Developers Microsoft Your Passion...Your Potential The Podcast Network The Podcast Network cameronreilly@gmail.com no http://msdev.thepodcastnetwork.com/wp-images/coverart_144x144.jpg TPN :: The Microsoft Developer Show http://msdev.thepodcastnetwork.com 144 144 Reposting the Moth on Cross Platform Development http://msdev.thepodcastnetwork.com/2006/10/10/reposting-the-moth-on-cross-platform-development/ http://msdev.thepodcastnetwork.com/2006/10/10/reposting-the-moth-on-cross-platform-development/#comments Mon, 09 Oct 2006 20:32:04 +0000 Nick Mobility Visual Studio http://msdev.thepodcastnetwork.com/2006/10/10/reposting-the-moth-on-cross-platform-development/ I’m not a big fan of reposting content that other people have already stated numerous times, but Daniel Moth has some exceptional posts that are worthy of some mention:

]]> http://msdev.thepodcastnetwork.com/2006/10/10/reposting-the-moth-on-cross-platform-development/feed/ Nick Randolph I%26#8217;m not a big fan of reposting content that other people have already stated numerous times, but Daniel Moth has some exceptional posts that are worthy of some mention: Retargetable (=256) Share Code (#if FULL_FRAME) Deploy to My Computer Resx I'm not a big fan of reposting content that other people have already stated numerous times, but Daniel Moth [1] has some exceptional posts that are worthy of some mention: Retargetable (=256) [2] Share Code (#if FULL_FRAME) [3] Deploy to My Computer [4] Resx compatibility for Smart Device projects [5] Another use of partial types [6] Not a strict subset [7] Sharing Cursor.WaitCursor and InputPanel in VS2005 [8] Dotnet changes [9] Speaking at MEDC 2006 [10] [1] http://msdev.thepodcastnetwork.comhttp://www.danielmoth.com/Blog [2] http://msdev.thepodcastnetwork.comhttp://www.danielmoth.com/Blog/2004/09/retargetable-256.html [3] http://msdev.thepodcastnetwork.comhttp://www.danielmoth.com/Blog/2004/09/share-code-if-fullframe_17.html [4] http://msdev.thepodcastnetwork.comhttp://www.danielmoth.com/Blog/2005/01/deploy-to-my-computer.html [5] http://msdev.thepodcastnetwork.comhttp://www.danielmoth.com/Blog/2005/08/resx-compatibility-for-smart-device.html [6] http://msdev.thepodcastnetwork.comhttp://www.danielmoth.com/Blog/2005/08/another-use-of-partial-types.html [7] http://msdev.thepodcastnetwork.comhttp://www.danielmoth.com/Blog/2005/08/not-strict-subset.html [8] http://msdev.thepodcastnetwork.comhttp://www.danielmoth.com/Blog/2005/08/sharing-cursorwaitcursor-and.html [9] http://msdev.thepodcastnetwork.comhttp://www.danielmoth.com/Blog/2005/09/dotnet-changes.html [10] http://msdev.thepodcastnetwork.comhttp://www.danielmoth.com/Blog/2006/05/speaking-at-medc-2006.html No No Dual Project for Cross Platform Development http://msdev.thepodcastnetwork.com/2006/10/05/dual-project-for-cross-platform-development/ http://msdev.thepodcastnetwork.com/2006/10/05/dual-project-for-cross-platform-development/#comments Wed, 04 Oct 2006 17:36:23 +0000 Nick Mobility Visual Studio http://msdev.thepodcastnetwork.com/2006/10/05/dual-project-for-cross-platform-development/ One of the topics that was covered in the show with Jeff Arnett is how you can aid cross platform development by using dual, or parallel, projects.  The premise is that for every desktop project, you have a parallel device project.  The projects reside in the same directory and use the same code files, which means that if you write code that will not compile on either the desktop or device it will display design-time errors in Visual Studio.

This seems a great idea in theory but the difficulty is trying to (a) get these projects setup and (b) maintaining them.  The hardest thing with Visual Studio is overriding its default behaviour.  For example when you create a new project, it will ALWAYS create a new directory to put it in.  Further, if you try and create a project in an existing directory Visual Studio will prevent you.  So, how do you setup two projects in the same directory? I will attempt to show you how you can get started.

Project Creation

  1. Open VS2005 and create a new Class Library project - Visual Basic –> Windows –> Class Library (for this example I will use a VB.NET project but this method works just as well in C#).  Give the project the name “MobileLibrary”; create a directory for the solution; name the solution “Mobility”
  2. Add a new device Class Library project to the existing solution - Visual Basic –> Smart Device –> Windows Mobile 5.0 Pocket PC –> Class Library (again I have chosed WM5 PPC but this should work for any of the smart device project types).  Give the project the name “MobileLibrary_CF”
  3. Exclude the device project from the solution
  4. Using File Explorer move the device project files (in this case “MobileLibrary_CF.vbproj” and “MobileLibrary_CF.vbproj.user” into the same folder as the desktop class library (in this case in the “MobileLibrary” folder)
  5. Add the device project into the existing solution (in this case from the “MobileLibrary” folder)
  6. You will probaby have 2 build errors relating to incompatibilities between the desktop and the device (AssemblyFileVersion and CompilerGeneratedAttribute are not supported on the device).  You can safetly remove these lines of code and hey presto you’re done!

Now you will have to agree this is a bit of a PITA if you have to do this process every time you want to create a new class library in an existing solution.  One way to get around this would be to create a multi-project template.  However, again you run into the issue where Visual Studio will not allow 2 projects to be created in the same directory….

]]> http://msdev.thepodcastnetwork.com/2006/10/05/dual-project-for-cross-platform-development/feed/ Nick Randolph One of the topics that was covered in the show with Jeff Arnett is how you can aid cross platform development by using dual, or parallel, projects.  The premise is that for every desktop project, you have a parallel device project.  The projects reside One of the topics that was covered in the show with Jeff Arnett is how you can aid cross platform development by using dual, or parallel, projects.  The premise is that for every desktop project, you have a parallel device project.  The projects reside in the same directory and use the same code files, which means that if you write code that will not compile on either the desktop or device it will display design-time errors in Visual Studio. This seems a great idea in theory but the difficulty is trying to (a) get these projects setup and (b) maintaining them.  The hardest thing with Visual Studio is overriding its default behaviour.  For example when you create a new project, it will ALWAYS create a new directory to put it in.  Further, if you try and create a project in an existing directory Visual Studio will prevent you.  So, how do you setup two projects in the same directory? I will attempt to show you how you can get started. Project Creation Open VS2005 and create a new Class Library project - Visual Basic --> Windows --> Class Library (for this example I will use a VB.NET project but this method works just as well in C#).  Give the project the name "MobileLibrary"; create a directory for the solution; name the solution "Mobility" Add a new device Class Library project to the existing solution - Visual Basic --> Smart Device --> Windows Mobile 5.0 Pocket PC --> Class Library (again I have chosed WM5 PPC but this should work for any of the smart device project types).  Give the project the name "MobileLibrary_CF" Exclude the device project from the solution Using File Explorer move the device project files (in this case "MobileLibrary_CF.vbproj" and "MobileLibrary_CF.vbproj.user" into the same folder as the desktop class library (in this case in the "MobileLibrary" folder) Add the device project into the existing solution (in this case from the "MobileLibrary" folder) You will probaby have 2 build errors relating to incompatibilities between the desktop and the device (AssemblyFileVersion and CompilerGeneratedAttribute are not supported on the device).  You can safetly remove these lines of code and hey presto you're done! Now you will have to agree this is a bit of a PITA if you have to do this process every time you want to create a new class library in an existing solution.  One way to get around this would be to create a multi-project template.  However, again you run into the issue where Visual Studio will not allow 2 projects to be created in the same directory.... No No