I saw this topic in the archives and since the message is more than 60
days old, couldn't comment on this.

The original thread suggests that since TCP/IP is used for comunication
between the computer and emulator, prescence of a firewall could be
responsible for the emulator running slowly.

Deployment of a simple native app (even with the emulator running)
takes more than a minute on an average. .NET CF takes close to 10 mins
(or more) to installed. .NET CF apps take 2+ mins to start.

There are times when there's as much as a 10 second delay in debug mode
when I move from one line to the next (F10).

I'm using Visual Studio 2005 and the WM5.0 SDK. My development computer
has XP firewall enabled, on top of which I'm behind a company firewall.
Is this the reason behind the sluggish perfomance of the emulator? Even
when I run it with Ctrl-F5, the processor usage spikes to 100%
frequently. The machine has an AMD Athlon XP 1700+ processor with 1 GB
RAM.

I'm sure the emulator can run faster, is there anything I can do to
speedup the emulator? Do I need admin privileges of any sort to do so?

Regards,
Abhijit.

Re: Old Topic: Pocket PC emulator slow on startup by Barry

Barry
Wed Jan 17 07:58:08 CST 2007

Visual Studio 2005 does not use networking to communicate with the
DeviceEmulator. The "DMA Bootstrap" and "DMA Transport" are both using COM
cross-process remoting, so they're quite speedy and are independent of all
networking technologies like firewall The first beta of VS2005 used TCP to
talk to the emulator, but we switched at ship to DMA for better performance
and reliability.

There are no settings to tune performance: it runs as fast as possible.
And your machine is plenty fast and has lots of RAM. So I'm not sure why
you are seeing such slowness. Could you post to the Device Emulator General
forum at http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=76&SiteID=1
and see if someone there can help?


Barry

"AB" <abjbhat@gmail.com> wrote in message
news:1168954956.528569.31330@v45g2000cwv.googlegroups.com...
>I saw this topic in the archives and since the message is more than 60
> days old, couldn't comment on this.
>
> The original thread suggests that since TCP/IP is used for comunication
> between the computer and emulator, prescence of a firewall could be
> responsible for the emulator running slowly.
>
> Deployment of a simple native app (even with the emulator running)
> takes more than a minute on an average. .NET CF takes close to 10 mins
> (or more) to installed. .NET CF apps take 2+ mins to start.
>
> There are times when there's as much as a 10 second delay in debug mode
> when I move from one line to the next (F10).
>
> I'm using Visual Studio 2005 and the WM5.0 SDK. My development computer
> has XP firewall enabled, on top of which I'm behind a company firewall.
> Is this the reason behind the sluggish perfomance of the emulator? Even
> when I run it with Ctrl-F5, the processor usage spikes to 100%
> frequently. The machine has an AMD Athlon XP 1700+ processor with 1 GB
> RAM.
>
> I'm sure the emulator can run faster, is there anything I can do to
> speedup the emulator? Do I need admin privileges of any sort to do so?
>
> Regards,
> Abhijit.
>

Re: Old Topic: Pocket PC emulator slow on startup by AB

AB
Wed Jan 17 23:06:55 CST 2007

Thanks for the link, will look in there as well.

Barry Bond [MS] wrote:
> Visual Studio 2005 does not use networking to communicate with the
> DeviceEmulator. The "DMA Bootstrap" and "DMA Transport" are both using COM
> cross-process remoting, so they're quite speedy and are independent of all
> networking technologies like firewall The first beta of VS2005 used TCP to
> talk to the emulator, but we switched at ship to DMA for better performance
> and reliability.
>
> There are no settings to tune performance: it runs as fast as possible.
> And your machine is plenty fast and has lots of RAM. So I'm not sure why
> you are seeing such slowness. Could you post to the Device Emulator General
> forum at http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=76&SiteID=1
> and see if someone there can help?
>
>
> Barry
>
> "AB" <abjbhat@gmail.com> wrote in message
> news:1168954956.528569.31330@v45g2000cwv.googlegroups.com...
> >I saw this topic in the archives and since the message is more than 60
> > days old, couldn't comment on this.
> >
> > The original thread suggests that since TCP/IP is used for comunication
> > between the computer and emulator, prescence of a firewall could be
> > responsible for the emulator running slowly.
> >
> > Deployment of a simple native app (even with the emulator running)
> > takes more than a minute on an average. .NET CF takes close to 10 mins
> > (or more) to installed. .NET CF apps take 2+ mins to start.
> >
> > There are times when there's as much as a 10 second delay in debug mode
> > when I move from one line to the next (F10).
> >
> > I'm using Visual Studio 2005 and the WM5.0 SDK. My development computer
> > has XP firewall enabled, on top of which I'm behind a company firewall.
> > Is this the reason behind the sluggish perfomance of the emulator? Even
> > when I run it with Ctrl-F5, the processor usage spikes to 100%
> > frequently. The machine has an AMD Athlon XP 1700+ processor with 1 GB
> > RAM.
> >
> > I'm sure the emulator can run faster, is there anything I can do to
> > speedup the emulator? Do I need admin privileges of any sort to do so?
> >
> > Regards,
> > Abhijit.
> >