ASP.net interface with windows API

[Michael Weyant]

Hey all,

I am looking for a method to have an ASP.net page perform remote
configuration of an embedded windows device..things like configuring TCP/IP
info, domain participation, computer name, proxy info, etc.

My intent was to have this device host an ASP page in IIS that would make
this possible by calling windows APIs...

First off, does this seem like a viable approach? And if so would one of you
be kind enough to point me in the right direction?

Michael

[John Saunders [MVP]]

"Michael Weyant" <mw*****@themarlincompany.comwrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...

Hey all,

I am looking for a method to have an ASP.net page perform remote
configuration of an embedded windows device..things like configuring
TCP/IP info, domain participation, computer name, proxy info, etc.

My intent was to have this device host an ASP page in IIS that would make
this possible by calling windows APIs...

First off, does this seem like a viable approach? And if so would one of
you be kind enough to point me in the right direction?

I presume that the embedded device supports .NET? Does the device support
the entire framework?

I don't see any reason why this couldn't work.
--
John Saunders [MVP]

[Spam Catcher]

"Michael Weyant" <mw*****@themarlincompany.comwrote in
news:#a**************@TK2MSFTNGP03.phx.gbl:

Hey all,

I am looking for a method to have an ASP.net page perform remote
configuration of an embedded windows device..things like configuring
TCP/IP info, domain participation, computer name, proxy info, etc.

My intent was to have this device host an ASP page in IIS that would
make this possible by calling windows APIs...

Most embedded machines do not have IIS - but if they do, then this could be
done.

First off, does this seem like a viable approach? And if so would one
of you be kind enough to point me in the right direction?

You would call the APIs as if it were a desktop application - no difference
if it's ASP.NET or Windows Forms.

Perhaps some security setting changes to the account which runs IIS, but
those sort of issues won't become apparent until you start development.