4

I've created some Web API methods in .NET 4 / Visual Studio 2010 (and have now ported it to VS 2013 RC).

I want to consume them from a Windows CE / Compact Framework app using RestSharp.

Regardless of how I call these methods, though, I need to know the IP Address to use for the app running the Web API methods. I can access it from a browser using "localhost" and the port number Visual Studio displays when running the View for the Web API project in the browser (works fine, returns XML in Chrome).

But: how can I call it from my Windows CE / Compact Framework app? The emulator in which I run it doesn't believe that it and localhost are really on the same machine, so I can't use that, nor the machine's actual IP address as, again, it is delusional about who/where it is.

So: what is the workaround? How can I test this?

More details about this can be seen here: RFC on HttpWebRequest vs RESTSharp from Windows CE / Compact Framework 3.5

UPDATE

Vasily, my guess was that you meant for me to do this:

enter image description here

...but that led to this:

enter image description here

Note: I get the same when I choose the other option from the dropdown asociated with the "Enable NE2000 PCMCIA network adapter and bind to:" czechbox, namely "Intel(R) 82579LM Gigabit Network Connection".

And trying to install http://go.microsoft.com/fwlink/?linkid=46859 (both the 64-bit and the 32-bit flavors) slapped me with:

enter image description here

So tell me, I implore: Is there balm in Gilead, so that there may be joy in Mudville tonight?

UPDATE 2

In step 6 (bullet 6), I did this:

enter image description here

...which got me first a message that the software didn't install correctly, with the option to retry or assert that, no, everything is really fine (I chose the latter), but then this:

enter image description here

...IOW, I don't make it to step/bullet point 7

Then again, this Peek cat did warn, "Note that this is very much a “works on my machine” experience. If it burns your house down, don’t hold me responsible."

My house didn't burn down (I don't think - I'm not there right now), but the process to extract the file did fail ignominiously.

Community
  • 1
  • 1
B. Clay Shannon-B. Crow Raven
  • 8,547
  • 144
  • 472
  • 862
  • 1
    Have you seen Brian Peek's [Windows Virtual PC and the Microsoft Device Emulator](http://brianpeek.com/post/2009/05/02/windows-virtual-pc-and-the-microsoft-device-emulator) article? Basically, you need to pull a file out of the installer, and he shows you how to do that. –  Oct 10 '13 at 20:25
  • @jp2code: Updated my post again with the results. – B. Clay Shannon-B. Crow Raven Oct 10 '13 at 22:17
  • What, exactly, is your development environment? I'm running under Win 7 64-bit and have none of the issue you're having. Are you running under a VM or something? – ctacke Oct 13 '13 at 20:58
  • Prior to porting, I had to use VS2003 in XP Mode, but now that it's being ported, I am also using 64-bit Windows 7. – B. Clay Shannon-B. Crow Raven Oct 14 '13 at 15:08
  • Clay, is this your article? http://www.codeproject.com/Articles/674088/Web-Site-Extreme-Makeover-Part-2-of-N –  Oct 29 '13 at 17:37
  • @jp2code: Jawohl, Herr Kommandant! Installment 3 should be live any hour, and #4 shortly thereafter. – B. Clay Shannon-B. Crow Raven Oct 29 '13 at 18:01

2 Answers2

1

You can use workstation network card by the emulator. Todo it you have to select "Use installed network card" checkbox and select the card from the list. after that you can use the workstation ip.

Vasiliy
  • 492
  • 3
  • 11
1

This was helpful for me:

Windows Virtual PC and the Microsoft Device Emulator

I've had to use it more than a couple of times.

I saved the file as a PDF to my network folder, so it took me a while to find the link.