On my machine I have VS 2003 and have just installed VS 2005. Taking to devices works fine in VS 2003, but I cannot connect correctly with VS 2005 to the emulators (I haven't tried a real device yet). I followed all the install instructions ( http://msdn.microsoft.com/mobility/windowsmobile/howto/windowsmobile5/install/default.aspx) and have ActiveSync 4.1 on the machine and this machine never had VS 2005 Beta on it. If I press on the device connect icon, the emulator (I have tried different ones and they have the default settings of DMA) will start, but VS says the connection failed and the system cannot find path specified. ( I have no idea what path it is referring to) I also try to start the emulators through the Device Emulator Manager and again the emulator starts, but I get an error of "Cannot connect to device 0x80070003" Do you have any ideas on how to get my emulators to connect with VS 2005? -- Thanks,
Hi Juan, The issue was first discovered on VS2005 Beta 2. You have to make sure RTM version is installed on the machine. If this is just the case, please do the following: 1. Shutdown VS2005 2. Backup/Delete all the files in "%USERPROFILE%\local settings\application data\Microsoft\CoreCon\1.0" 3. Restart VS2005 If this does not resolve the problem, I will provide you with steps to completely uninstall any Pre-RTM versions of VS 2005. Thanks. Best regards, WenJun Zhang Microsoft Online Partner Support This posting is provided "AS IS" with no warranties, and confers no rights.
I NEVER had any of the beta VS 2005 on this machine, I am now only installing VS 2005 for the first time on this machine. Activesync works fine with my Dell Axim, so I know that is installed ok, but I just cannot talk to the emulators. I searched for the directory you did mention. I have only one coreCon directory and that is under PFiles\common files\ microsoft shared\. But that has a lot of dlls in, so I am assuming that is not the directory you were talking about. Also the only local settings directory I have is under doc and Settings\All users and there does look like anything there beside my temperary internet files. Any additional help in getting VS 2005 to connect to the emulators would be appreciated. Thanks, Juan [quoted text, click to view] ""WenJun Zhang[msft]"" wrote: > Hi Juan, > > The issue was first discovered on VS2005 Beta 2. You have to make sure RTM > version is installed on the machine. If this is just the case, please do > the following: > > 1. Shutdown VS2005 > 2. Backup/Delete all the files in "%USERPROFILE%\local settings\application > data\Microsoft\CoreCon\1.0" > 3. Restart VS2005 > > If this does not resolve the problem, I will provide you with steps to > completely uninstall any Pre-RTM versions of VS 2005. > > Thanks. > > Best regards, > > WenJun Zhang > Microsoft Online Partner Support > > This posting is provided "AS IS" with no warranties, and confers no rights. > > >
Hi Juan, This may be a hidden directory. You can directly input %USERPROFILE%\local settings\application data\Microsoft\CoreCon\1.0 in Start->Run or the address bar of IE\Windows Explorer. %USERPROFILE% is a System variable points to your current logon user's profile directory, e.g: C:\Documents and Settings\<account>\ Best regards, WenJun Zhang Microsoft Online Partner Support This posting is provided "AS IS" with no warranties, and confers no rights.
I found the directory and deleted it. I now can connect successfully and even cradle successfully using the device emulator manager. But when I go to deploy I get an error saying it is unable to start my program. "An error occurred that usually indicated a corrupt installation (code 0x8007007e). If the problem persists, repair your Visual Studio installation via "add or Remove Programs in the Control Panel. So I did a repair and end up with the same error when I go to deploy. Any new Ideas? Thanks,
Hi Juan, The error is most likely caused some required files/dlls missing on the Device. For example, if you are developing MFC applications which is using dynamic linking, you may switch it to static linking to have a try. Thanks. Best regards, WenJun Zhang Microsoft Online Partner Support This posting is provided "AS IS" with no warranties, and confers no rights.
No, I tried several simple .NET Compact Framework apps. In looking at it all the files are on the device. I can actually run the application in the emulator manually finding it with file explorer. So it is like VS installs everything but cannot then start and debug, like the error I mentioned suggests. Again, if there is anything I could try to narrow this down, I would happy to do that since I really would like to get this to work so I can work with the compact framework under VS 2005. -- Thanks, Juan [quoted text, click to view] ""WenJun Zhang[msft]"" wrote: > Hi Juan, > > The error is most likely caused some required files/dlls missing on the > Device. For example, if you are developing MFC applications which is using > dynamic linking, you may switch it to static linking to have a try. > > Thanks. > > Best regards, > > WenJun Zhang > Microsoft Online Partner Support > > This posting is provided "AS IS" with no warranties, and confers no rights. > > >
I don't know if there was something specific you wanted me to look at , but I did see something that did not look correct. I started my emulator by connecing to it. Then I started my program (UnitTest) and selected the proper emulator that was already running. VS then was busy downloading files and when it got to the end where it should jump into the debugger I got the error I discussed earlier. The interesting part in looking in the file monitor, it it trying to open d:\microsoft visual studio 8\common7\ide\%CSIDL_PROGRAM_FILES%\UnitTest\UnitTest.exe. My code files exist on d:\projectsmobile\units\unitsTest\bin\debug\unittest.exe. And on my device all files are in \Program Files\unittest and if I select the unittest.exe on the emulator device, it all works. How can I get the path straightened out? -- Thanks, Juan [quoted text, click to view] ""WenJun Zhang[msft]"" wrote: > Hi Juan, > > If so, to further troubleshoot this issue, you may run filemon/regmon to > trace the I/O during the error occurs. Let's see if there is any obvious > file or registry missing or corruption. > > Filemon: > http://www.sysinternals.com/Utilities/Filemon.html > > Regmon: > http://www.sysinternals.com/Utilities/Regmon.html > > Best regards, > > WenJun Zhang > Microsoft Online Partner Support > > This posting is provided "AS IS" with no warranties, and confers no rights. > > >
Hi Juan, Please open the project's property in VS2005. In Debug section->Start Action, check which setting is corrently used. You can also use 'Start external program' to explicitly specify the path to test. Best regards, WenJun Zhang Microsoft Online Partner Support This posting is provided "AS IS" with no warranties, and confers no rights.
Start Project is checked. If I run without the debugger it runs just fine, so it just seems to be an issue with starting the debugger. -- Thanks, Juan [quoted text, click to view] ""WenJun Zhang[msft]"" wrote: > Hi Juan, > > Please open the project's property in VS2005. In Debug section->Start > Action, check which setting is corrently used. > > You can also use 'Start external program' to explicitly specify the path to > test. > > Best regards, > > WenJun Zhang > Microsoft Online Partner Support > > This posting is provided "AS IS" with no warranties, and confers no rights. > > >
Hi Juan, Do you mean if you select 'Start external program' and point the debugger to the correct .exe file, the problem still persists? Thanks. Best regards, WenJun Zhang Microsoft Online Partner Support This posting is provided "AS IS" with no warranties, and confers no rights.
The managed program will run on the emulator if I select it using the file manager on the emulator or if in VS 2005 I select start without debugging. If I choose to debug my simple application, it gives the error I discussed earlier. On using the "Start external Program", instead of "Start Project", I guess I don't know what I should put in there. I tried "%CSIDL_PROGRAM_FILES%\DeviceApplication1\DeviceApplication1.exe", but that gave me the same error. You can see the connection and everything is obviously working fine, it is just the debugger is confused as to where to find the application. -- Thanks, Juan [quoted text, click to view] ""WenJun Zhang[msft]"" wrote: > Hi Juan, > > Do you mean if you select 'Start external program' and point the debugger > to the correct .exe file, the problem still persists? > > Thanks. > > Best regards, > > WenJun Zhang > Microsoft Online Partner Support > > This posting is provided "AS IS" with no warranties, and confers no rights. > > >
Hi Juan, I mean when using "Start external Program", you can explicitly set the path to: d:\projectsmobile\units\unitsTest\bin\debug\unittest.exe Best regards, WenJun Zhang Microsoft Online Partner Support This posting is provided "AS IS" with no warranties, and confers no rights.
We are not making progress here. D:\projectsmobile is my desktop directory. What I am trying to do is debug on my emulator device. By running filemon we can see the debugger was trying to use a combination of the desktop and emulator path. I really need to get this problem solved soon, so if there is any other information I can provide for you to help move this forward, please let me know. -- Thanks, Juan [quoted text, click to view] ""WenJun Zhang[msft]"" wrote: > Hi Juan, > > I mean when using "Start external Program", you can explicitly set the path > to: > > d:\projectsmobile\units\unitsTest\bin\debug\unittest.exe > > Best regards, > > WenJun Zhang > Microsoft Online Partner Support > > This posting is provided "AS IS" with no warranties, and confers no rights. > > >
Hi Juan, Please understand this is no longer a VS setup issue but related to mobility dev and debugging. I will ping our VS Mobile Dev engineer for assistance on it. If there are any suggestions or ideas, I will update here to let you know. Thanks & best regards, WenJun Zhang Microsoft Online Partner Support This posting is provided "AS IS" with no warranties, and confers no rights.
Hi Juan, I'm still contacting our mobility engineer about this issue. Just a side note, you may also post a thread to our Compact Framework newsgroup which may be an appropriate place for you to get ideas and suggestions of this issue: microsoft.public.dotnet.framework.compactframework Best regards, WenJun Zhang Microsoft Online Partner Support This posting is provided "AS IS" with no warranties, and confers no rights.
Don't see what you're looking for? Try a search.
|