Forum

Problem with Meridian/P Getting Started application in Visual Studio 2008 Professional
Last Post 02 Apr 2010 07:31 PM by ondrejandrej. 5 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
ondrejandrej
New Member
New Member
Posts:11

--
15 Mar 2010 12:24 PM

    Hello,

    I cannot do the step 14. in the Getting Started Guide:

    14. Right-click on the project in Solution Explorer and select Properties.

    14. Select the .NET Micro Framework tab, and then select USB as the Deployment Transport. You should see "Meridian_a7e70ea2" appear as the device.

    Project Properties in Visual C# do not open as a separate window, but rather as a tabbed document next to the source code files. I guess this could be the difference between Express and Professional editions of Visual Studio.

    There is no tab named ".NET Micro Framework", nor "Deployment Transport" setting.

    BTW you have a couple of error in your Getting Started Guide. For example, you guide the user to install .NET Micro Framework SDK 3.0, but then you guide him to install the latest version of Device Solutions SDK, which requires .NET Micro Framework SDK 4.0!
    ondrejandrej
    New Member
    New Member
    Posts:11

    --
    15 Mar 2010 12:30 PM


    And I forgot to mention, that I'm using Windows 7. It might matter.
    mwelford
    Basic Member
    Basic Member
    Posts:298

    --
    15 Mar 2010 02:19 PM
    Thanks for finding those bugs! They should be fixed now.
    For C# express, I've just tested it and you should see the same thing as you do in VS2008 Professional. It sounds like the Microsoft .NET Micro Framework SDK did not install correctly on your machine.

    You should be fine with Windows 7. I have a 64-bit Win7 test machine that runs everything OK.
    ondrejandrej
    New Member
    New Member
    Posts:11

    --
    16 Mar 2010 08:29 AM
    I reinstalled .NET Framework SDK and it works very well! The trouble might have been that I did not remove .NET Framework 3.0 before installing v. 4.0.
    mwelford
    Basic Member
    Basic Member
    Posts:298

    --
    16 Mar 2010 08:30 AM
    That would do it. Thanks for letting us know.
    ondrejandrej
    New Member
    New Member
    Posts:11

    --
    02 Apr 2010 07:31 PM
    You can mark this topic as resolved.
    You are not authorized to post a reply.


    Active Forums 4.3