
Signature
Chris Tacke, Embedded MVP
OpenNETCF Consulting
Managed Code in an Embedded World
www.OpenNETCF.com
> Yes, it was a reported bug:
> http://bugzilla.opennetcf.com/show_bug.cgi?id=107
>
> If you've purchased the SDF, send an email to support[at]OpenNETCF.com to
> get a patch, otherwise you'll have to wait for our next release.
I'm using the community edition, so I guess I'll have to wait.
With the Extensions for VS product, it comes with the sources. Would
this mean that we could, in theory, fix it ourselves? If so, it might
be a cheaper option than doing with the maintenance agreement option.
Thanks
D
<ctacke/> - 30 Aug 2007 15:05 GMT
> With the Extensions for VS product, it comes with the sources. Would this
> mean that we could, in theory, fix it ourselves? If so, it might be a
> cheaper option than doing with the maintenance agreement option.
Not just "in theory". We can send you the fixed code and you can rebuild it
yourself, we just aren't at a state where we can recompile and release
another version the entire community edition for this fix.

Signature
Chris Tacke, Embedded MVP
OpenNETCF Consulting
Managed Code in an Embedded World
www.OpenNETCF.com
Paul G. Tobey [eMVP] - 30 Aug 2007 16:19 GMT
David,
You can manually make this change, if you want to and, when the fix comes
out, easily drop back to it. The IP address is stored in the registry at
the location I mentioned in my other message. Make the changes you need to
EnableDHCP and IPAddress, SubnetMask, and DefaultGateway, and then do an
Adapter.RebindAdapter() and the new information will be picked up from the
registry.
Paul T.
>> Yes, it was a reported bug:
>> http://bugzilla.opennetcf.com/show_bug.cgi?id=107
[quoted text clipped - 11 lines]
>
> D
David Hearn - 31 Aug 2007 11:37 GMT
> David,
>
[quoted text clipped - 6 lines]
>
> Paul T.
Excellent - I'll give that a go.
Thanks
David