Debug WM 6.5 application without ActiveSync connection - connection

Is there a way to debug my application (running on Windows Mobile 6.5, deployed on Visual Studio 2005) without ActiveSync?I want to go through some connection problems and with the ActiveSync-connection always enabled, I can't really test the WLAN and/or GPRS-module with my application.
I tried disabling the USB-connection in ActiveSync, but then Visual Studio cannot connect to my device and I am not able to debug my project. (It does disable the connection on my device though).
Am i missing some settings I can change on my device and/or ActiveSync?

It seems that it is not possible to do this when you are trying to debug over WWAN/GPRS.
But it works if you connect your device to your office network/the network you are also developing with, see Debugging Visual Studio applications with no ActiveSync support.
Note: this may not work with all devices running WM6.5, in my case this was a Psion EP10 and it worked.

This one
http://www.turboirc.com/ppc/s5.htm
works fine for me with VS 2008 and WM 6.5
Take a look at
http://blogs.msdn.com/b/vsdteam/archive/2005/04/28/413304.aspx
as well.

Related

Xamarin VS Windows - IPhone does not show up

I'm using Visual Studio for Windows and I have a Xamarin Forms app for Android and iOS. I mostly test physically on Android (since that is much easier) and I have tested on an IPhone as well about a year ago, which worked fine (without a mac). Now I plugged it in again and it doesn't work anymore: the IPhone does not show up in the debugging list.
I have:
Apple Developer account and I'm connected with this account from Visual Studio
Identifier for Bundle
Profile (created by VS itself, with Type 'Development')
What am I missing here? I haven't added the provisioning profile in my solution, is that something that needs to be done? Am I missing another step?
I hope someone can help.
For the exact breakdown on how to setup and get started with your iOS solution, follow Microsoft's Xamarin iOS on Windows guide.
The tl;dr though is: you absolutely need a Mac to run a Xamarin iOS project, even on windows. I do not know how you had your project setup last time, however this has been the case since Xamarin's debut. Although, you could also just have access to a Mac through network connection instead of having a physical Mac. Without a physical device, you can use the Mac's ios simulator. If you are planning on using a physical iphone though, said device needs to be plugged into the Mac and not the windows machine. Later MacOS do support wireless connections of trusted devices, but it is still a wireless connection from the iphone to the mac (needing to be on the same network).

How can I inspect element in an iPhone X's browser?

I have a CSS bug (visual difference) that seems to happen only in iPhone X devices.
what I would usually do in cases like these is use the inspector tool in the browser the bug occurs to find the rule I wrote that is not cross browser, and do a trial and error in the inspector tool until I find what works cross browser and cross platform.
knowing that iPhone uses safari browser - I installed safari on my windows PC but couldn't reproduce the bug.
how can I simulate a browser in a iPhone on my windows PC? or is there another way to find the quirk in this case in order to fix it?
I can't afford a mac.
I have windows 10 on my PC but can also use a linux distribution if needed.
also, this cannot be debugged in a cloud because the security team won't allow the code to be hosted on an external cloud at the stage of development.
As far as I know, your best/cheapest approach would be to run MacOS within a Virtual Machine and then perform the steps Neal suggested.
But keep in mind that you need to run the network config of your Virtual Machine in "Bridge Mode" otherwise your virtual macos can't see any devices on your network.

usb debugging, mono for android on vmware windows 8?

I'm using the android emulator in this environment (VMware fusion5/windows 8/vs2012-mono for android) and it's working ok for degugging, but I'd like to switch a license to this machine so I can use it for actual device testing. Since you are limited with the number of times you can repurpose a license with xamarin, I'd like to know if it'll actually work before I activate the license on this environment. Anyone doing it?
Thanks.
In case anyone needs to know, it works fine. VMware sees the device when it's plugged in and asks if you want to connect to windows or mac. Choosing windows lets adb see the device.

Problems with my first Visual Studio iOS project

I just tried to start a simple iOS project in Visual Studio, and it's saying that it cannot find a Mac Build Host. Most frustrating of all, the Xamarin site has no information at all on what a Mac Build Host is. I've popped up the command prompt in Windows and perfectly able to ping my Mac machine, so it's definitely viewable from Windows.
I'm guessing it's got to be some kind of a background process that needs to run on the Mac, but nowhere in the Xamarin site tells me where I can get it.
Help!
<vent>
P.S. I'm seriously having second thoughts about "cross platform" and "portability" and "reuse existing C# skills" jargon from Xamarin. It was way, way easier to get my first app started in simple Objective-C. Xamarin's approach feels like "we will ship you a broken product for $999, and you can help us figure out how to make this more marketable".
</vent>
Edit: After reading everyone's posts, I think I will just use the Xamarin Studio rather than take the Visual Studio approach. It seems like the less complicated approach in the long run for someone like me. Thanks to everyone for your post!
The Xamarin docs site has instructions on how to set up your Mac to act as an iOS build host for Visual Studio. I agree this isn't very clear from the "Connect to a Xamarin.iOS Build Host" dialog, so I've filed a bug.
You can also use Xamarin Studio to develop Xamarin.iOS apps on the Mac. It uses the same project/solution format as Visual Studio, so you can share the solution with VS.
The Mac Build Host is a process which runs on the network-hosted mac you need to connect to from your Windows machine, in order to perform the final app compile and build. I have just installed iOS for Visual Studio, and I had to create a Xamarin account that was associated with the VS install. Also, I had to install Xamarin.iOS on the Mac itself, instructions here:
http://docs.xamarin.com/guides/ios/getting_started/installation/mac/
What wasn't explained properly was that I then had to close VS, open it and create a new iOS project. At this point, a wizard was initiated which used the Xamarin Bonjour service to locate our networked mac and use that as the build host. All the bits came installed with the Xamarin installer, I just had to initiate them by opening up a project.
Obviously this will be different for you using Xamarin Studio, but have you tried creating a new a project to see if this initiates a wizard? Or do you need to install the iOS on your mac as well as Windows?
I have to admit, I'm not entirely sure what is meant by "Mac Build Host" either. I would expect to find something like that if you were using Visual Studio to build with, not Xamarin Studio.
My best guess is that perhaps Xamarin Studio doesn't "see" your iOS development tools setup somehow? Can you go into the Add-in Manager and see what version of iOS development you have in there?
Sorry you're having a bad time with it so far. I've been using it for awhile and it's been fantastic for me so far.
Do you have bonjour installed on your windows machine? This is required for Xamarin studio on windows to talk to your mac build host. Also you need to set up the relationship as follows.
Section 3.1
For anyone else who might have spent a few days going around in circles the answer above that states you need to close VS, open it and create a new iOS project holds the key.
Xamarin really needs to make this much clearer!
Andreas
One further thing I've noticed is that despite my setting the Xamarin Bonjour service to start automatically, it somehow gets reset to Manual. The Xamarin plugin opens the services MMC when I launch Visual Studio and open an existing project when this occurs.
During debugging it's all too easy to stop the VS debugger before the iOS Simulator on the Mac machine has been halted. It works fine if you click on the iPhone Simulator bottom button then command-Q to close the simulator. That drops VS out of debug.
If though VS is stopped before the simulator in some cases this kills the connection and it needs VS to be closed down and restarted. Once or twice it has corrupted the iOS simulator and it comes up with an empty iPhone graphic, instead of the default Photos, Contacts Settings etc icons. In that case close and reopen it and as you start the simulator click on the iOS Simulator menu, then Reset Contents and Settings. That purges the corrupt state and it's all ok after that.
Overall it works well enough to not get in the way of development but any improvements by the Xamarin team are welcomed.

Windows phone development - can't run emulator with internet connection

Background
A few years ago I was developing for C#, WPF and Silverlight and then moved to developing for Android.
I've decided to give Windows phone a try, and install the newest Visual Studio Pro 2012 with its Windows phone sdk, together with the latest version of Windows - windows 8 pro.
I've created a new Windows phone project hoping I will start learning from a hello world project, and I've launched the emulator .
Some specs information
OS is windows 8 pro (final) . 64 bit CPU .
Visual Studio Pro 2012
Windows phone sdk 8
Connected by usb to a wireless D-Link device (DWA-140) .
The problem
Just as soon as I've started the emulator, a dialog came asking if I want to enable networking:
When I chose that I want, an error has appeared:
After selecting ok, the emulator crashed.
Knowing how to search for solutions on the internet, I've found a few (like here and here ) that suggested me to delete the network switches, create an internal switch, and whatnot.
The question
I don't understand what I'm doing wrong, and this is just my starting point. Can anyone please help me with this error and how to make the emulator work?
Please tell me the exact steps that I need to take.
EDIT: after uninstallation of anything related to VS and WP , i've re-installed them both and i still get the same errors.
Not only that , but when trying to create a new external switch (which some websites offered) , it showed me the next error :
How could such a basic feature of an emulator be missing out of the box ?
You might try a couple of things.
First, verify the network connection settings for the "vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch)" adapter.
To do so, open "Control Panel\Network and Internet\Network Connections" in Control Panel. Right click on the "vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch)" adapter, and choose "Properties". Under "This connection uses the following items:" verify that ONLY the following options are selected:
Client for Microsoft Networks
QoS Packet Scheduler
File and Printer Sharing for Microsoft Networks
Microsoft LLDP Protocol Driver
Link-Layer Topology Discovery Mapper I/O Driver
Link-Layer Topology Discovery Responder
Internet Protocol Version 6 (TCP/IPv6)
Internet Protocol Version 4 (TCP/IPv4)
In addition, you may want to review the network adapter settings for the emulator image in "Hyper-V Manager"
Verify the network adapters that are shown are valid. You might try disabling some (like the adapters connected to the WiFi or Wired Ethernet adapters on your machine) if the adapters they are bound to are not currently enabled in the OS.
Let me know if that helps!
I suspect you may be running afoul of UAC. As you've noted, it's trying to create a virtual device. Doing so requires elevated permissions. If I were you I would either run VS2012 as Administrator or completely disable UAC until it's all installed and configured, and then you can turn UAC back on if you prefer it on. I think Allen's comment about manually creating a VM with the appropriate networking is astute and a worthwhile experiment, since it sidesteps the possible UAC issues.

Resources