nsoftware / IPWorks

  • Thread starter Thread starter Earl
  • Start date Start date
E

Earl

Anyone have any luck using their CF tools in VS2005? Their website is
strangely silent about what versions of Visual Studio they support.
 
Their January newsletter:
Visual Studio 2005 & Borland Delphi 2006 Update

All IP*Works! and IBiz Integrator products have been upgraded to include
additional support for Visual Studio 2005 and Borland Delphi 2006. All
current customers can download the update online.


/ Peter
 
Earl said:
Anyone have any luck using their CF tools in VS2005? Their website is
strangely silent about what versions of Visual Studio they support.
Click to expand...

If you visit www.nsoftware.com, right there on the front page it gives
details of our VS2005 support.

Yes, we support VS2005. The components currently do not show in the toolbox
unless the project targetframeworkversion is 1, however you can simply
reference and use them as you would normally.

Lance
 
Oh.. I thought the newsletter I received on the 25th meant visual support
was included

(All IP*Works! and IBiz Integrator products have been upgraded to include
additional support for Visual Studio 2005 and Borland Delphi 2006.)

What does "additional support" mean then?

/ Peter
 
Perhaps the other components are compatible, but Ipports simply does not
work in VS2005. I will send this on to the regular support page, but I
thought you might be interested in what I found.

I set up a project in VS2003, with a simple connect, disconnect. All methods
and properties work as advertised in VS2003. However ...

Moved it over to VS2005, imported the (single) reference to Ipports. The
project would both build and deploy, but on the same connect IP, the Connect
method puked and spit out 3 exceptions:

System.IO.FileNotFound,
System.Net.Sockets.SocketException, and
System.NotSupportedException
 
Earl said:
Perhaps the other components are compatible, but Ipports simply does not
work in VS2005. I will send this on to the regular support page, but I
thought you might be interested in what I found.
Click to expand...

If you haven't already submitted this through the regular support page -
please do. I have no problem using the IPPortS component in VS2005, nor do
other users. Perhaps there is something specific to your test.

Lance
 
Peter Hartlén said:
Oh.. I thought the newsletter I received on the 25th meant visual support
was included

(All IP*Works! and IBiz Integrator products have been upgraded to include
additional support for Visual Studio 2005 and Borland Delphi 2006.)

What does "additional support" mean then?

/ Peter
Click to expand...

Before this update, there was no specific support for VS2005 or Delphi 2006.
Although the components worked in both of these environments, we didn't do
anything special to accomodate them.

With this update, the installer has been updated to install the components
to the toolboxes of both VS2005 and BDS2006. In the case of VS2005 - this
doesn't apply for .Net CF projects yet. Also specifically for VS2005 we
have updated our ASP.Net Edition to include a web control dll. The update
also includes integrated help as well as demo updates.

Lance
 
Thanks for your response Lance. That at least gives me the confidence that
Ipports is usable in VS2005, as all our development is now turning in that
direction for WM 5.0. I've sent the project on over to support.
 
Earl said:
Thanks for your response Lance. That at least gives me the confidence that
Ipports is usable in VS2005, as all our development is now turning in that
direction for WM 5.0. I've sent the project on over to support.
Click to expand...

Hi Earl, when I saw your message here I grabbed your email from our support
box and gave your project a run. I was able to get connected with no
problems. I'm not sure what the problem is, but I sent you an email
detailing the steps I took.

Lance
 
Back
Top