Does anyone use .NET on XPe?

I've posted a similar question once w/o any responses. Is there anything
required beyond the .NET component to make it operational? I am unable to
run any .NET compiled programs. I receive an error immediately upon
execution saying an exception that couldn't be handled has occurred. Any
thoughts or ideas?

Kevin Goddard wrote:

>Is there anything required beyond the .NET component to make it operational?

Not as far as I am aware as long as it's dependencies are satisfied.

What version of the .NET Framework is your application developed for?
XPe only supports 1.0 out of the box, if you need 1.1 then you will
have to install it onto your runtime or else wait for the MS
component.

Andy.

I plan to use it but have not run it on my XPe images yet.
My developers are using XP pro images on beta units until I get my XPe image
ready.
I'd like an update on when a .Net 1.1 component will be ready.
MS is pushing .net and they are pushing XP, but the .net 1.1 updated
component is lagging behind

David
"Andy Pont AMIAP" <apont@nospam.bluechiptechnology.co.uk> wrote in message
news:rc0qov4lopeifkl2r9du73hjq4i65pgrjh@4ax.com...
> Kevin Goddard wrote:
>
> >Is there anything required beyond the .NET component to make it
operational?
>
> Not as far as I am aware as long as it's dependencies are satisfied.
>
> What version of the .NET Framework is your application developed for?
> XPe only supports 1.0 out of the box, if you need 1.1 then you will
> have to install it onto your runtime or else wait for the MS
> component.
>
> Andy.
>

We have released XPe images for 2 different embedded devices, both of which
have .NET 1.1 installed. Our application suite running on the devices
requires it. .NET is installed just before the applications are installed.

--
Regards.
Mark K Vallevand

"Kevin Goddard" <khgoddard@cox.net> wrote in message
news:%237K51bqkDHA.3256@tk2msftngp13.phx.gbl...
> I've posted a similar question once w/o any responses. Is there anything
> required beyond the .NET component to make it operational? I am unable to
> run any .NET compiled programs. I receive an error immediately upon
> execution saying an exception that couldn't be handled has occurred. Any
> thoughts or ideas?
>
>

Kevin,
Depending on your application, you may have to use the MSI installer to make
sure and get all of the files that are required to run your application..

Regards,

Sean Gahan


"Kevin Goddard" <khgoddard@cox.net> wrote in message
news:%237K51bqkDHA.3256@tk2msftngp13.phx.gbl...
> I've posted a similar question once w/o any responses. Is there anything
> required beyond the .NET component to make it operational? I am unable to
> run any .NET compiled programs. I receive an error immediately upon
> execution saying an exception that couldn't be handled has occurred. Any
> thoughts or ideas?
>
>

I'm working on it, all i can ask is that you be patient with me, it's high
on my priority list.
Thanks.
Andy
--

This posting is provided "AS IS" with no warranties, and confers no rights.
"David Ditch" <dditch1@deletediscomcast.net> wrote in message
news:8_SdndSCjeCgyBCiRVn-hg@comcast.com...
> I plan to use it but have not run it on my XPe images yet.
> My developers are using XP pro images on beta units until I get my XPe
image
> ready.
> I'd like an update on when a .Net 1.1 component will be ready.
> MS is pushing .net and they are pushing XP, but the .net 1.1 updated
> component is lagging behind
>
> David
> "Andy Pont AMIAP" <apont@nospam.bluechiptechnology.co.uk> wrote in message
> news:rc0qov4lopeifkl2r9du73hjq4i65pgrjh@4ax.com...
> > Kevin Goddard wrote:
> >
> > >Is there anything required beyond the .NET component to make it
> operational?
> >
> > Not as far as I am aware as long as it's dependencies are satisfied.
> >
> > What version of the .NET Framework is your application developed for?
> > XPe only supports 1.0 out of the box, if you need 1.1 then you will
> > have to install it onto your runtime or else wait for the MS
> > component.
> >
> > Andy.
> >
>
>

Andy,
Are there any problems if the dotnetfx 1.1 is run on xpe?

Sean Gahan



"Andy Allred [MS]" <andyall@online.microsoft.com> wrote in message
news:OtxXry4kDHA.708@TK2MSFTNGP10.phx.gbl...
> I'm working on it, all i can ask is that you be patient with me, it's high
> on my priority list.
> Thanks.
> Andy
> --
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "David Ditch" <dditch1@deletediscomcast.net> wrote in message
> news:8_SdndSCjeCgyBCiRVn-hg@comcast.com...
> > I plan to use it but have not run it on my XPe images yet.
> > My developers are using XP pro images on beta units until I get my XPe
> image
> > ready.
> > I'd like an update on when a .Net 1.1 component will be ready.
> > MS is pushing .net and they are pushing XP, but the .net 1.1 updated
> > component is lagging behind
> >
> > David
> > "Andy Pont AMIAP" <apont@nospam.bluechiptechnology.co.uk> wrote in
message
> > news:rc0qov4lopeifkl2r9du73hjq4i65pgrjh@4ax.com...
> > > Kevin Goddard wrote:
> > >
> > > >Is there anything required beyond the .NET component to make it
> > operational?
> > >
> > > Not as far as I am aware as long as it's dependencies are satisfied.
> > >
> > > What version of the .NET Framework is your application developed for?
> > > XPe only supports 1.0 out of the box, if you need 1.1 then you will
> > > have to install it onto your runtime or else wait for the MS
> > > component.
> > >
> > > Andy.
> > >
> >
> >
>
>

Hi Sean.
If you're asking about running the .Net v1.1 installer for full XP-Pro to
expand it onto a runtime, theoretically this will work. Other people have
reported success doing just that. It's not recommended, but for testing
purposes this could be done as a temporary solution until the component is
released.

Again, thank you for your patience so far! <grin>

Andy

--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================


"Sean Gahan" <sean@optistreams.net> wrote in message
news:uzSCty$kDHA.2964@tk2msftngp13.phx.gbl...
> Andy,
> Are there any problems if the dotnetfx 1.1 is run on xpe?
>
> Sean Gahan
>
>
>
> "Andy Allred [MS]" <andyall@online.microsoft.com> wrote in message
> news:OtxXry4kDHA.708@TK2MSFTNGP10.phx.gbl...
> > I'm working on it, all i can ask is that you be patient with me, it's
high
> > on my priority list.
> > Thanks.
> > Andy
> > --
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > "David Ditch" <dditch1@deletediscomcast.net> wrote in message
> > news:8_SdndSCjeCgyBCiRVn-hg@comcast.com...
> > > I plan to use it but have not run it on my XPe images yet.
> > > My developers are using XP pro images on beta units until I get my XPe
> > image
> > > ready.
> > > I'd like an update on when a .Net 1.1 component will be ready.
> > > MS is pushing .net and they are pushing XP, but the .net 1.1 updated
> > > component is lagging behind
> > >
> > > David
> > > "Andy Pont AMIAP" <apont@nospam.bluechiptechnology.co.uk> wrote in
> message
> > > news:rc0qov4lopeifkl2r9du73hjq4i65pgrjh@4ax.com...
> > > > Kevin Goddard wrote:
> > > >
> > > > >Is there anything required beyond the .NET component to make it
> > > operational?
> > > >
> > > > Not as far as I am aware as long as it's dependencies are satisfied.
> > > >
> > > > What version of the .NET Framework is your application developed
for?
> > > > XPe only supports 1.0 out of the box, if you need 1.1 then you will
> > > > have to install it onto your runtime or else wait for the MS
> > > > component.
> > > >
> > > > Andy.
> > > >
> > >
> > >
> >
> >
>
>

Andy,
That is what we are doing now, can you be more descriptive of what short
comings I may have.

Regards,

Sean Gahan

"Andy Allred [MS]" <andyall@online.microsoft.com> wrote in message
news:evhpqIBlDHA.964@TK2MSFTNGP10.phx.gbl...
> Hi Sean.
> If you're asking about running the .Net v1.1 installer for full XP-Pro to
> expand it onto a runtime, theoretically this will work. Other people have
> reported success doing just that. It's not recommended, but for testing
> purposes this could be done as a temporary solution until the component is
> released.
>
> Again, thank you for your patience so far! <grin>
>
> Andy
>
> --
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> ==========================================================
>
>
> "Sean Gahan" <sean@optistreams.net> wrote in message
> news:uzSCty$kDHA.2964@tk2msftngp13.phx.gbl...
> > Andy,
> > Are there any problems if the dotnetfx 1.1 is run on xpe?
> >
> > Sean Gahan
> >
> >
> >
> > "Andy Allred [MS]" <andyall@online.microsoft.com> wrote in message
> > news:OtxXry4kDHA.708@TK2MSFTNGP10.phx.gbl...
> > > I'm working on it, all i can ask is that you be patient with me, it's
> high
> > > on my priority list.
> > > Thanks.
> > > Andy
> > > --
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > "David Ditch" <dditch1@deletediscomcast.net> wrote in message
> > > news:8_SdndSCjeCgyBCiRVn-hg@comcast.com...
> > > > I plan to use it but have not run it on my XPe images yet.
> > > > My developers are using XP pro images on beta units until I get my
XPe
> > > image
> > > > ready.
> > > > I'd like an update on when a .Net 1.1 component will be ready.
> > > > MS is pushing .net and they are pushing XP, but the .net 1.1 updated
> > > > component is lagging behind
> > > >
> > > > David
> > > > "Andy Pont AMIAP" <apont@nospam.bluechiptechnology.co.uk> wrote in
> > message
> > > > news:rc0qov4lopeifkl2r9du73hjq4i65pgrjh@4ax.com...
> > > > > Kevin Goddard wrote:
> > > > >
> > > > > >Is there anything required beyond the .NET component to make it
> > > > operational?
> > > > >
> > > > > Not as far as I am aware as long as it's dependencies are
satisfied.
> > > > >
> > > > > What version of the .NET Framework is your application developed
> for?
> > > > > XPe only supports 1.0 out of the box, if you need 1.1 then you
will
> > > > > have to install it onto your runtime or else wait for the MS
> > > > > component.
> > > > >
> > > > > Andy.
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Sean,
Determining the dependencies is the issue here. Plus needing to add
dependencies just for the *installer* mechanism itself, like the Windows
Installer Service or whatever it's using.

I'd rather not get deeply involved in understanding the dependencies to do
this because I only want to support one way installing via the component. An
hour spent figuring out a hack is an hour I'm not working on componentizing
the .Net v1.1 package <grin>

If you have trouble installing it, please start a new thread asking for the
dependencies that other people have used in their runtimes just to get it on
there. I'm sure someone will help out with that.

Sorry if it's not much help Sean.
Thanks.
Andy
--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================


"Sean Gahan" <sean@optistreams.net> wrote in message
news:ubbYloBlDHA.2528@TK2MSFTNGP12.phx.gbl...
> Andy,
> That is what we are doing now, can you be more descriptive of what short
> comings I may have.
>
> Regards,
>
> Sean Gahan
>
> "Andy Allred [MS]" <andyall@online.microsoft.com> wrote in message
> news:evhpqIBlDHA.964@TK2MSFTNGP10.phx.gbl...
> > Hi Sean.
> > If you're asking about running the .Net v1.1 installer for full XP-Pro
to
> > expand it onto a runtime, theoretically this will work. Other people
have
> > reported success doing just that. It's not recommended, but for testing
> > purposes this could be done as a temporary solution until the component
is
> > released.
> >
> > Again, thank you for your patience so far! <grin>
> >
> > Andy
> >
> > --
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > ==========================================================
> >
> >
> > "Sean Gahan" <sean@optistreams.net> wrote in message
> > news:uzSCty$kDHA.2964@tk2msftngp13.phx.gbl...
> > > Andy,
> > > Are there any problems if the dotnetfx 1.1 is run on xpe?
> > >
> > > Sean Gahan
> > >
> > >
> > >
> > > "Andy Allred [MS]" <andyall@online.microsoft.com> wrote in message
> > > news:OtxXry4kDHA.708@TK2MSFTNGP10.phx.gbl...
> > > > I'm working on it, all i can ask is that you be patient with me,
it's
> > high
> > > > on my priority list.
> > > > Thanks.
> > > > Andy
> > > > --
> > > >
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > > "David Ditch" <dditch1@deletediscomcast.net> wrote in message
> > > > news:8_SdndSCjeCgyBCiRVn-hg@comcast.com...
> > > > > I plan to use it but have not run it on my XPe images yet.
> > > > > My developers are using XP pro images on beta units until I get my
> XPe
> > > > image
> > > > > ready.
> > > > > I'd like an update on when a .Net 1.1 component will be ready.
> > > > > MS is pushing .net and they are pushing XP, but the .net 1.1
updated
> > > > > component is lagging behind
> > > > >
> > > > > David
> > > > > "Andy Pont AMIAP" <apont@nospam.bluechiptechnology.co.uk> wrote in
> > > message
> > > > > news:rc0qov4lopeifkl2r9du73hjq4i65pgrjh@4ax.com...
> > > > > > Kevin Goddard wrote:
> > > > > >
> > > > > > >Is there anything required beyond the .NET component to make it
> > > > > operational?
> > > > > >
> > > > > > Not as far as I am aware as long as it's dependencies are
> satisfied.
> > > > > >
> > > > > > What version of the .NET Framework is your application developed
> > for?
> > > > > > XPe only supports 1.0 out of the box, if you need 1.1 then you
> will
> > > > > > have to install it onto your runtime or else wait for the MS
> > > > > > component.
> > > > > >
> > > > > > Andy.
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>