• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 404
  • Last Modified:

VS 2005 deploy to virtual mobile device - failure due to security issue?

HI all,
It seems that this was working last week, but now when I try to debug a program written for a mobile device the deploy part fails due to some sort of security issue I think.

The virtual device is connected and cradled, I can pass files back and forth using windows explorer, so I know it is connected, but the deploy always fails.

Any Ideas on how to fix this?

Thanks,
Pat
0
phmurphy
Asked:
phmurphy
  • 16
  • 10
2 Solutions
 
alexey_gusevCommented:
try to perform a hard reset to this virtual device - I reckon this is an emulator for WM ?
0
 
phmurphyAuthor Commented:
I just did a soft reset with no luck, but do I really have to do a hard reset?  Is there a way to save the current configuration before doing that?
0
 
phmurphyAuthor Commented:
Here is a screen shot of the error in VS2005 deploy error
0
Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

 
alexey_gusevCommented:
soft reset won't help you surely.

you can save the configuration, but I suspect it is something in your configuration that causes the problem. Could you please post the exact error message you're getting?

and I wonder what prevents you from doing hard reset on the emulator? any specific components you need to re-install?
0
 
phmurphyAuthor Commented:
I went ahead and did the hard reset.  I guess I was afraid that it would zero out everything, which it didn't.  However, I still had the same error.  I did the hard reset while the virtual device was NOT connected, then I reconnected.
0
 
alexey_gusevCommented:
hmm, I've missed the message while typing my previous post :)

perhaps you could try to uninstall the driver for this device via Device Manager on your PC and then cradle the emulator again, but I believe hard reset might be MUCH easier and faster.
0
 
phmurphyAuthor Commented:
the hared reset doesn't actually clear away everything.  I also tried to clear saved state, then do a reset, but I still have everything I originally had installed.
0
 
alexey_gusevCommented:
how did you do the reset?
0
 
phmurphyAuthor Commented:
OK, I finally got it cleared.  I had to shut down the virtual device FIRST.  Then clear the state and do a reset.  I will now try the debug deploy to see what happens.
0
 
phmurphyAuthor Commented:
Just trying the debug/deploy failed with the same error.  I also tried just a deploy, that failed.  I am going to try to copy the cab and install first, then try the debug/deploy
0
 
phmurphyAuthor Commented:
Still with the same error.
0
 
alexey_gusevCommented:
I assume all SPs are installed. perhaps try to uninstall device driver for this connection and re-cradle the emulator.
0
 
alexey_gusevCommented:
besides, try to google this exact error, you'll find all sorts of reasons and solutions why it happened - could be anything from firewall to corrupted/missing files somewhere
0
 
phmurphyAuthor Commented:
All windows and microsoft things are up to date.  I am not sure how to go about uninstalling the device driver or even what that means.  Does that mean uninstalling the WM6 Professional SDK?
0
 
phmurphyAuthor Commented:
Thanks, I will try some of those suggestions found in google.
0
 
alexey_gusevCommented:
"uninstalling the device driver" - right click on My Computer and select Manage, then go to Device Manager. You should see something under Mobile Devices.

I'm not sure it will help resolve this particular problem because it seems more like VS issue rather than driver's
0
 
phmurphyAuthor Commented:
Here is a summary:
Tools > connect to device - did not work and that includes after cradling
I deleted the .vbproj.user file and that didn't work.
I tried to deploy while connected but not cradled, - no luck
Will try more.
0
 
phmurphyAuthor Commented:
I turned off all firewalls - Norton and MS
I rebuilt the CAB file and did a rebuild of the solution file.
I checked to make sure the target device and the connected/cradle device were the same, and I could copy files back and forth.

Still same error.

I did find a very similar project that does allow the debug/deploy to work.  I see that there is a greyed out folder References under (not in) the greyed out My Projects folder. Is that a possible issue?  How do I get that same references folder to show up in the problem project?
0
 
phmurphyAuthor Commented:
Here is a screen shot of the references folder from the project that does work.  I am focusing on this because it is the only difference I can see so far between a project where debug works and one where it doesn't work. How can I create this folder in the problem project?this folder is missing in the problem project
0
 
alexey_gusevCommented:
does your project contain references? this folder is virtual and  included by default and is populated when you add references. Its content is taken from your csproj file selecting all "Reference" nodes in ItemGroup.

could you try recreate your project or even simply create dummy app and try to deploy/debug it?
0
 
phmurphyAuthor Commented:
My program is in vb, so I should look for a vbproj file I guess.  I actually found another project that also debugs properly and it too has the virtual folder.  I don't know how I lost them, but how can I regenerat them.  I have some references in the cab file that I don't include because they are built into the WM6 devices.  How can I regenerate that virutal folder?
0
 
alexey_gusevCommented:
I don't know how to do it 'officially' in VS, but try to edit your working project file and copy/paste ItemGroup with references into non-working project file, then reopen it in VS and see what happens
0
 
hjgodeCommented:
Check your device's connection settings in Visual Studio:
click Tools menu in VS and then Options
then scroll down to Device Tools and click the (+) to unfold the subitems
then click your device emulator in the list of emulators and then [Properties]
Transport should be DMA as within WMDC/ActiveSync connection settings
Bootstrapper should be "Device emulator startup provider"
If both is right and you can still not connect, I am stuck too

 Device Options - Emulator Images
To deploy and debug applications, VS has to copy over some files. If these files are corrupt debugging and deploy will fail.
Debugging is done via a TCP/IP or DMA connection. TCP/IP requires manual startup of the device side debug provider and a manual setup of the connection.

When you start to debug your app, is the emulator started from Visual Studio or do you start it manually before?
0
 
phmurphyAuthor Commented:
Darn,that didn't fix it.  I found some old .vbproj files and now I have restored the virtual folders but I still get the same error.  I will continue comparing it with project that does debug properly.
0
 
alexey_gusevCommented:
I bet it's easier to create new project and add all the stuff from the old one. A bit of a headache, but probably will do the trick
0
 
phmurphyAuthor Commented:
hjgode - I know it is connected because I can pass files with windows explorer.  I connect and cradle the device before I try the debug.  All the settings in the Device Tools are as you described.

alexey - I will start to try to duplicate the project and see if that works.
0
 
phmurphyAuthor Commented:
The web had some comments about having a file in the project files that either couldn't be found or needed to be found.  My solution was that I had a folder in the help files that was not included in the help files that were part of the cab, but it was in the folder that was supposed to be sent to the cab.  I just deleted it from the solution explorer and the debug worked again.

Confusing so let me try to explain it again.  I had a Help folder of files that were included in the cab build list.  The actual folder as seen on the list of items in the solution explorer had an additional folder that was NOT included in the build list.  I deleted it from the solution explorer and everything worked OK.

Thanks for the help.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

  • 16
  • 10
Tackle projects and never again get stuck behind a technical roadblock.
Join Now