.NET Framework 2.0 component

  • Thread starter Thread starter Virg
  • Start date Start date
V

Virg

Hello,

I use TD for XPE SP 2 FP 2007

When I do a check dependency on my image, I get the following error:
Error 1109: Component: ".NET Framework 2.0 [Version 5.1.2600.3333,
R3333]" conflicts with other enabled components in the configuration

In my original image, I only have .NET Framework 1.1 component.
But in the process of "checking dependencies", I can also read that:
Info 106: Adding component: ".NET Framework 2.0 [Version
5.1.2600.3333, R3333]", origin: "ASP.NET 1.1 [Version 5.1.2600.3333,
R3333]"

Why?

Thank you.
 
The .net 1.1 components can reside in the same database with .net 2.0,
but can not reside in the same configuration. For the most part .net 2.0
is backwards compatible with .net 1.1 and your older application should
still just work if you only have .net 2.0 in the configuration.

If you really need both versions in the runtime, then you should choose
one of these (preferably .net 1.1) to be in the configuration via TD,
and install the second one from the desktop using the installer that is
also used for XP Pro, this will enable true side by side versions of the
framework on the runtime. This blog article covers the dependency
requirements for the .net 2.0 installer:
http://blogs.msdn.com/embedded/archive/2005/11/23/496333.aspx

The blog article refers to a macro component you can download,
unfortunately the external server i'm hosting that on is offline at the
moment but expect it to be online again tonight. If you still have
trouble connecting or downloading, contact me at wecrt @ microsoft.com
and our customer strike team can e-mail you the .net 2.0 macro component
mentioned in the blog.

-andy
 
Thank you Andy for your answer.

But I have a little last interrogation:

When I'm doing a check dependency, why do it says:
Info 106: Adding component: ".NET Framework 2.0 [Version
5.1.2600.3333, R3333]", origin: "ASP.NET 1.1 [Version 5.1.2600.3333,
R3333]"

Looks like ASP.NET is dependant of .NET Framework 2.0

But is wasn't the case before I migrate to FP 2007.

Any ideas?

Virginie


Andy Allred [MS] a écrit :
The .net 1.1 components can reside in the same database with .net 2.0,
but can not reside in the same configuration. For the most part .net 2.0
is backwards compatible with .net 1.1 and your older application should
still just work if you only have .net 2.0 in the configuration.

If you really need both versions in the runtime, then you should choose
one of these (preferably .net 1.1) to be in the configuration via TD,
and install the second one from the desktop using the installer that is
also used for XP Pro, this will enable true side by side versions of the
framework on the runtime. This blog article covers the dependency
requirements for the .net 2.0 installer:
http://blogs.msdn.com/embedded/archive/2005/11/23/496333.aspx

The blog article refers to a macro component you can download,
unfortunately the external server i'm hosting that on is offline at the
moment but expect it to be online again tonight. If you still have
trouble connecting or downloading, contact me at wecrt @ microsoft.com
and our customer strike team can e-mail you the .net 2.0 macro component
mentioned in the blog.

-andy

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no rights.


Hello,

I use TD for XPE SP 2 FP 2007

When I do a check dependency on my image, I get the following error:
Error 1109: Component: ".NET Framework 2.0 [Version 5.1.2600.3333,
R3333]" conflicts with other enabled components in the configuration

In my original image, I only have .NET Framework 1.1 component.
But in the process of "checking dependencies", I can also read that:
Info 106: Adding component: ".NET Framework 2.0 [Version
5.1.2600.3333, R3333]", origin: "ASP.NET 1.1 [Version 5.1.2600.3333,
R3333]"

Why?

Thank you.
Click to expand...
Click to expand...
 
Hi, what you're seeing is correct. ASP.net should require the .net
framework. If the previous version did not have this dependency
relationship then it was probably a bug. Were you ever able to use
ASP.net when .net framework feature was *not* in your previous runtime?

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no rights.


Thank you Andy for your answer.

But I have a little last interrogation:

When I'm doing a check dependency, why do it says:
Info 106: Adding component: ".NET Framework 2.0 [Version
5.1.2600.3333, R3333]", origin: "ASP.NET 1.1 [Version 5.1.2600.3333,
R3333]"

Looks like ASP.NET is dependant of .NET Framework 2.0

But is wasn't the case before I migrate to FP 2007.

Any ideas?

Virginie


Andy Allred [MS] a écrit :

The .net 1.1 components can reside in the same database with .net 2.0,
but can not reside in the same configuration. For the most part .net 2.0
is backwards compatible with .net 1.1 and your older application should
still just work if you only have .net 2.0 in the configuration.

If you really need both versions in the runtime, then you should choose
one of these (preferably .net 1.1) to be in the configuration via TD,
and install the second one from the desktop using the installer that is
also used for XP Pro, this will enable true side by side versions of the
framework on the runtime. This blog article covers the dependency
requirements for the .net 2.0 installer:
http://blogs.msdn.com/embedded/archive/2005/11/23/496333.aspx

The blog article refers to a macro component you can download,
unfortunately the external server i'm hosting that on is offline at the
moment but expect it to be online again tonight. If you still have
trouble connecting or downloading, contact me at wecrt @ microsoft.com
and our customer strike team can e-mail you the .net 2.0 macro component
mentioned in the blog.

-andy

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no rights.


Hello,

I use TD for XPE SP 2 FP 2007

When I do a check dependency on my image, I get the following error:
Error 1109: Component: ".NET Framework 2.0 [Version 5.1.2600.3333,
R3333]" conflicts with other enabled components in the configuration

In my original image, I only have .NET Framework 1.1 component.
But in the process of "checking dependencies", I can also read that:
Info 106: Adding component: ".NET Framework 2.0 [Version
5.1.2600.3333, R3333]", origin: "ASP.NET 1.1 [Version 5.1.2600.3333,
R3333]"

Why?

Thank you.
Click to expand...
Click to expand...
Click to expand...
 
In fact, it seems that the new component for ASP.net 1.1 [Version
5.1.2600.3333,R3333] has a dependency with framework 2.0... and not
with framework .NET 1.1 as before. I think that I will have to
downgrade my ASP.net 1.1 component to SP2 (and not SP2 FP 2007 as
actually). I think that looks like a bug. Agree Andy?

Virginie
Hi, what you're seeing is correct. ASP.net should require the .net
framework. If the previous version did not have this dependency
relationship then it was probably a bug. Were you ever able to use
ASP.net when .net framework feature was *not* in your previous runtime?

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no rights.


Thank you Andy for your answer.

But I have a little last interrogation:

When I'm doing a check dependency, why do it says:
Info 106: Adding component: ".NET Framework 2.0 [Version
5.1.2600.3333, R3333]", origin: "ASP.NET 1.1 [Version 5.1.2600.3333,
R3333]"

Looks like ASP.NET is dependant of .NET Framework 2.0

But is wasn't the case before I migrate to FP 2007.

Any ideas?

Virginie


Andy Allred [MS] a écrit :

The .net 1.1 components can reside in the same database with .net 2.0,
but can not reside in the same configuration. For the most part .net 2..0
is backwards compatible with .net 1.1 and your older application should
still just work if you only have .net 2.0 in the configuration.

If you really need both versions in the runtime, then you should choose
one of these (preferably .net 1.1) to be in the configuration via TD,
and install the second one from the desktop using the installer that is
also used for XP Pro, this will enable true side by side versions of the
framework on the runtime. This blog article covers the dependency
requirements for the .net 2.0 installer:
http://blogs.msdn.com/embedded/archive/2005/11/23/496333.aspx

The blog article refers to a macro component you can download,
unfortunately the external server i'm hosting that on is offline at the
moment but expect it to be online again tonight. If you still have
trouble connecting or downloading, contact me at wecrt @ microsoft.com
and our customer strike team can e-mail you the .net 2.0 macro component
mentioned in the blog.

-andy

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no rights.



Virg wrote:

Hello,

I use TD for XPE SP 2 FP 2007

When I do a check dependency on my image, I get the following error:
Error 1109: Component: ".NET Framework 2.0 [Version 5.1.2600.3333,
R3333]" conflicts with other enabled components in the configuration

In my original image, I only have .NET Framework 1.1 component.
But in the process of "checking dependencies", I can also read that:
Info 106: Adding component: ".NET Framework 2.0 [Version
5.1.2600.3333, R3333]", origin: "ASP.NET 1.1 [Version 5.1.2600.3333,
R3333]"

Why?

Thank you.
Click to expand...
Click to expand...
Click to expand...
 
I'll forward the thread and see if we can figure it out. You should
either remove both v1.1 components or both v2.0 components, the v1.1
should not depend on v2.0.

Thank you!

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no rights.


In fact, it seems that the new component for ASP.net 1.1 [Version
5.1.2600.3333,R3333] has a dependency with framework 2.0... and not
with framework .NET 1.1 as before. I think that I will have to
downgrade my ASP.net 1.1 component to SP2 (and not SP2 FP 2007 as
actually). I think that looks like a bug. Agree Andy?

Virginie
Hi, what you're seeing is correct. ASP.net should require the .net
framework. If the previous version did not have this dependency
relationship then it was probably a bug. Were you ever able to use
ASP.net when .net framework feature was *not* in your previous runtime?

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no rights.


Thank you Andy for your answer.

But I have a little last interrogation:

When I'm doing a check dependency, why do it says:
Info 106: Adding component: ".NET Framework 2.0 [Version
5.1.2600.3333, R3333]", origin: "ASP.NET 1.1 [Version 5.1.2600.3333,
R3333]"

Looks like ASP.NET is dependant of .NET Framework 2.0

But is wasn't the case before I migrate to FP 2007.

Any ideas?

Virginie


Andy Allred [MS] a écrit :



The .net 1.1 components can reside in the same database with .net 2.0,
but can not reside in the same configuration. For the most part .net 2.0
is backwards compatible with .net 1.1 and your older application should
still just work if you only have .net 2.0 in the configuration.

If you really need both versions in the runtime, then you should choose
one of these (preferably .net 1.1) to be in the configuration via TD,
and install the second one from the desktop using the installer that is
also used for XP Pro, this will enable true side by side versions of the
framework on the runtime. This blog article covers the dependency
requirements for the .net 2.0 installer:
http://blogs.msdn.com/embedded/archive/2005/11/23/496333.aspx

The blog article refers to a macro component you can download,
unfortunately the external server i'm hosting that on is offline at the
moment but expect it to be online again tonight. If you still have
trouble connecting or downloading, contact me at wecrt @ microsoft.com
and our customer strike team can e-mail you the .net 2.0 macro component
mentioned in the blog.

-andy

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no rights.



Virg wrote:


Hello,

I use TD for XPE SP 2 FP 2007

When I do a check dependency on my image, I get the following error:
Error 1109: Component: ".NET Framework 2.0 [Version 5.1.2600.3333,
R3333]" conflicts with other enabled components in the configuration

In my original image, I only have .NET Framework 1.1 component.
But in the process of "checking dependencies", I can also read that:
Info 106: Adding component: ".NET Framework 2.0 [Version
5.1.2600.3333, R3333]", origin: "ASP.NET 1.1 [Version 5.1.2600.3333,
R3333]"

Why?

Thank you.
Click to expand...
Click to expand...
Click to expand...
 
Lynda confirmed this is in fact a bug that was introduced into the
asp.net v1.1 component when the servicing updates were incorporated into
it for the feature pack. We will file a bug on this so that asp.net v1.1
only depends on .net v1.1.

Thank you

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no rights.


I'll forward the thread and see if we can figure it out. You should
either remove both v1.1 components or both v2.0 components, the v1.1
should not depend on v2.0.

Thank you!

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no
rights.


In fact, it seems that the new component for ASP.net 1.1 [Version
5.1.2600.3333,R3333] has a dependency with framework 2.0... and not
with framework .NET 1.1 as before. I think that I will have to
downgrade my ASP.net 1.1 component to SP2 (and not SP2 FP 2007 as
actually). I think that looks like a bug. Agree Andy?

Virginie
Hi, what you're seeing is correct. ASP.net should require the .net
framework. If the previous version did not have this dependency
relationship then it was probably a bug. Were you ever able to use
ASP.net when .net framework feature was *not* in your previous runtime?

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no
rights.



Virg wrote:

Thank you Andy for your answer.

But I have a little last interrogation:

When I'm doing a check dependency, why do it says:
Info 106: Adding component: ".NET Framework 2.0 [Version
5.1.2600.3333, R3333]", origin: "ASP.NET 1.1 [Version 5.1.2600.3333,
R3333]"

Looks like ASP.NET is dependant of .NET Framework 2.0

But is wasn't the case before I migrate to FP 2007.

Any ideas?

Virginie


Andy Allred [MS] a écrit :



The .net 1.1 components can reside in the same database with .net
2.0,
but can not reside in the same configuration. For the most part
.net 2.0
is backwards compatible with .net 1.1 and your older application
should
still just work if you only have .net 2.0 in the configuration.

If you really need both versions in the runtime, then you should
choose
one of these (preferably .net 1.1) to be in the configuration via TD,
and install the second one from the desktop using the installer
that is
also used for XP Pro, this will enable true side by side versions
of the
framework on the runtime. This blog article covers the dependency
requirements for the .net 2.0 installer:
http://blogs.msdn.com/embedded/archive/2005/11/23/496333.aspx

The blog article refers to a macro component you can download,
unfortunately the external server i'm hosting that on is offline
at the
moment but expect it to be online again tonight. If you still have
trouble connecting or downloading, contact me at wecrt @
microsoft.com
and our customer strike team can e-mail you the .net 2.0 macro
component
mentioned in the blog.

-andy

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers
no rights.



Virg wrote:


Hello,

I use TD for XPE SP 2 FP 2007

When I do a check dependency on my image, I get the following error:
Error 1109: Component: ".NET Framework 2.0 [Version
5.1.2600.3333,
R3333]" conflicts with other enabled components in the configuration

In my original image, I only have .NET Framework 1.1 component.
But in the process of "checking dependencies", I can also read that:
Info 106: Adding component: ".NET Framework 2.0 [Version
5.1.2600.3333, R3333]", origin: "ASP.NET 1.1 [Version 5.1.2600.3333,
R3333]"

Why?

Thank you.
Click to expand...
Click to expand...
Click to expand...
 
Virg,

Thanks for the info. I have opened the bug. This is a workaround that you
can implement at present- not elegant but it solves the issue if you are
needing ASP 1.1 in your image.

In TD, satify all the deps that do not pertain to .NET 2.0 (i.e ignore any
tasks that tell you to resolve .NET 2.0 issue). Just before building, delete
..NET 2.0 from the config (and do not re-run check deps).
Finally, copy the aspnet_filter.dll from your SP2 repository (
{67C85615-B0C5-42EA-8B8A-E8AB47DB2B1D}) to your runtime and overwrite the
one that is there (WINDOWS\Microsoft.NET\Framework\v1.1.4322).
--
Thanks.

Lynda [MS]
"This posting is provided "AS IS" with no warranties, and confers no rights"
Andy Allred said:
Lynda confirmed this is in fact a bug that was introduced into the asp.net
v1.1 component when the servicing updates were incorporated into it for
the feature pack. We will file a bug on this so that asp.net v1.1 only
depends on .net v1.1.

Thank you

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no
rights.


I'll forward the thread and see if we can figure it out. You should
either remove both v1.1 components or both v2.0 components, the v1.1
should not depend on v2.0.

Thank you!

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no
rights.


In fact, it seems that the new component for ASP.net 1.1 [Version
5.1.2600.3333,R3333] has a dependency with framework 2.0... and not
with framework .NET 1.1 as before. I think that I will have to
downgrade my ASP.net 1.1 component to SP2 (and not SP2 FP 2007 as
actually). I think that looks like a bug. Agree Andy?

Virginie

Andy Allred [MS] wrote:

Hi, what you're seeing is correct. ASP.net should require the .net
framework. If the previous version did not have this dependency
relationship then it was probably a bug. Were you ever able to use
ASP.net when .net framework feature was *not* in your previous runtime?

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no
rights.



Virg wrote:

Thank you Andy for your answer.

But I have a little last interrogation:

When I'm doing a check dependency, why do it says:
Info 106: Adding component: ".NET Framework 2.0 [Version
5.1.2600.3333, R3333]", origin: "ASP.NET 1.1 [Version 5.1.2600.3333,
R3333]"

Looks like ASP.NET is dependant of .NET Framework 2.0

But is wasn't the case before I migrate to FP 2007.

Any ideas?

Virginie


Andy Allred [MS] a écrit :



The .net 1.1 components can reside in the same database with .net
2.0,
but can not reside in the same configuration. For the most part .net
2.0
is backwards compatible with .net 1.1 and your older application
should
still just work if you only have .net 2.0 in the configuration.

If you really need both versions in the runtime, then you should
choose
one of these (preferably .net 1.1) to be in the configuration via TD,
and install the second one from the desktop using the installer that
is
also used for XP Pro, this will enable true side by side versions of
the
framework on the runtime. This blog article covers the dependency
requirements for the .net 2.0 installer:
http://blogs.msdn.com/embedded/archive/2005/11/23/496333.aspx

The blog article refers to a macro component you can download,
unfortunately the external server i'm hosting that on is offline at
the
moment but expect it to be online again tonight. If you still have
trouble connecting or downloading, contact me at wecrt @
microsoft.com
and our customer strike team can e-mail you the .net 2.0 macro
component
mentioned in the blog.

-andy

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no
rights.



Virg wrote:


Hello,

I use TD for XPE SP 2 FP 2007

When I do a check dependency on my image, I get the following error:
Error 1109: Component: ".NET Framework 2.0 [Version
5.1.2600.3333,
R3333]" conflicts with other enabled components in the configuration

In my original image, I only have .NET Framework 1.1 component.
But in the process of "checking dependencies", I can also read that:
Info 106: Adding component: ".NET Framework 2.0 [Version
5.1.2600.3333, R3333]", origin: "ASP.NET 1.1 [Version 5.1.2600.3333,
R3333]"

Why?

Thank you.
Click to expand...
Click to expand...
Click to expand...
 
Great! Thank you Andy and Lynda!

Virg,

Thanks for the info. I have opened the bug. This is a workaround that you
can implement at present- not elegant but it solves the issue if you are
needing ASP 1.1 in your image.

In TD, satify all the deps that do not pertain to .NET 2.0 (i.e ignore any
tasks that tell you to resolve .NET 2.0 issue). Just before building, delete
.NET 2.0 from the config (and do not re-run check deps).
Finally, copy the aspnet_filter.dll from your SP2 repository (
{67C85615-B0C5-42EA-8B8A-E8AB47DB2B1D}) to your runtime and overwrite the
one that is there (WINDOWS\Microsoft.NET\Framework\v1.1.4322).
--
Thanks.

Lynda [MS]
"This posting is provided "AS IS" with no warranties, and confers no rights"
Andy Allred said:
Lynda confirmed this is in fact a bug that was introduced into the asp.net
v1.1 component when the servicing updates were incorporated into it for
the feature pack. We will file a bug on this so that asp.net v1.1 only
depends on .net v1.1.

Thank you

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no
rights.


I'll forward the thread and see if we can figure it out. You should
either remove both v1.1 components or both v2.0 components, the v1.1
should not depend on v2.0.

Thank you!

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no
rights.



Virg wrote:
In fact, it seems that the new component for ASP.net 1.1 [Version
5.1.2600.3333,R3333] has a dependency with framework 2.0... and not
with framework .NET 1.1 as before. I think that I will have to
downgrade my ASP.net 1.1 component to SP2 (and not SP2 FP 2007 as
actually). I think that looks like a bug. Agree Andy?

Virginie

Andy Allred [MS] wrote:

Hi, what you're seeing is correct. ASP.net should require the .net
framework. If the previous version did not have this dependency
relationship then it was probably a bug. Were you ever able to use
ASP.net when .net framework feature was *not* in your previous runtime?

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no
rights.



Virg wrote:

Thank you Andy for your answer.

But I have a little last interrogation:

When I'm doing a check dependency, why do it says:
Info 106: Adding component: ".NET Framework 2.0 [Version
5.1.2600.3333, R3333]", origin: "ASP.NET 1.1 [Version 5.1.2600.3333,
R3333]"

Looks like ASP.NET is dependant of .NET Framework 2.0

But is wasn't the case before I migrate to FP 2007.

Any ideas?

Virginie


Andy Allred [MS] a écrit :



The .net 1.1 components can reside in the same database with .net
2.0,
but can not reside in the same configuration. For the most part .net
2.0
is backwards compatible with .net 1.1 and your older application
should
still just work if you only have .net 2.0 in the configuration.

If you really need both versions in the runtime, then you should
choose
one of these (preferably .net 1.1) to be in the configuration via TD,
and install the second one from the desktop using the installer that
is
also used for XP Pro, this will enable true side by side versions of
the
framework on the runtime. This blog article covers the dependency
requirements for the .net 2.0 installer:
http://blogs.msdn.com/embedded/archive/2005/11/23/496333.aspx

The blog article refers to a macro component you can download,
unfortunately the external server i'm hosting that on is offline at
the
moment but expect it to be online again tonight. If you still have
trouble connecting or downloading, contact me at wecrt @
microsoft.com
and our customer strike team can e-mail you the .net 2.0 macro
component
mentioned in the blog.

-andy

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no
rights.



Virg wrote:


Hello,

I use TD for XPE SP 2 FP 2007

When I do a check dependency on my image, I get the following error:
Error 1109: Component: ".NET Framework 2.0 [Version
5.1.2600.3333,
R3333]" conflicts with other enabled components in the configuration

In my original image, I only have .NET Framework 1.1 component.
But in the process of "checking dependencies", I can also read that:
Info 106: Adding component: ".NET Framework 2.0 [Version
5.1.2600.3333, R3333]", origin: "ASP.NET 1.1 [Version 5.1.2600.3333,
R3333]"

Why?

Thank you.
Click to expand...
Click to expand...
Click to expand...
 
Andy:
Here's a good question for you.....

I've reviewed your info on the MS Website regarding the
MICROSOFT.NET\Framework issues I have a problem installing my HP OfficeJet
7310 printer regarding this issue. I was on the phone with HP Tech Support
(in New Delhi, India) and after (2) "glorious hours" attempting to install
this printer (Step 3 of 4 at 14% I was only at 67Kbs/sec. download time).
I've attempted installing this HP Printer (3) times....uninstall, reboot,
install .... error.....uninstall, reboot....etc.

JUST when I think I've fixed this issue the HP Tech Support tells me that
the download time is TOO SLOW and to stop the installation. After much
troubleshooting he directed me toward the errors page (in the MS Directory)
and stated it was a NETFX.MSI file so......

I went to MicroSoft Website and downloaded this file and I get this error
(below):
=======================
Microsoft .NET Framework 2.0 Setup
Error 25013 failed to install assembly
C:/windows/microsoft.net/framework/v2.0.50727/microsoft.vsa.dll because
strong name signature couldn't be verified. Was the assembly built
delay-signed?
========================

Where does "strong name signature couldn't be verified?" Was the assembly
built delay signed? (I have no idea what this means.

Secondly, I get an Error I get when I tried to install the .Net Framework
2.0 and the reporting details state:
=========================
This error report includes information regarding the condition of
SETUP.exe when the problem occured. The operating system version and
computer hardware in use your digital product ID which could be used to
identify your license and the IP address of your computer.
==================
(OK....what does this mean?)

Is this NET FRAMEWORK (2.0) really necessary to HP OfficeJet 7310 (All in
One) printer?
I've gone to my directory:
C:/windows/microsoft.net/framework
Under my director I see these folders .......
=========================
v1.0.3705
v1.1.4322
v2.0.50727

I see the V2.0.50727 file but because of the error when I've tried to run
the SETUP.exe file for dotnetfx 2.0 (.exe) and I keep getting errors on this.
Your help and assistance would be greatly appreciated.

I should DELETE the v2.0.50727 folder in this directory since it only has
(4) items in it and it didn't complete the install.

I inserted my original WINDOWS XP PRO (CD) and copied the DOTNETFIX on the
desktop but I don't want to run it (yet) because it's only v1.1.4322.573 set
up.
The current verison I have in my folder now is v1.1.4322.

The v1.1.4322.573 set up that I copied from my WINXP Pro CD appears to be
the NEW extension versus the one that's currently in my folder? How could
that be?

I look forward to your diligent assistance in this matter (Soon!).
Thanks!
Bill :)
 
Andy:
Here's a good question for you.....

I've reviewed your info on the MS Website regarding the
MICROSOFT.NET\Framework issues I have a problem installing my HP OfficeJet
7310 printer regarding this issue. I was on the phone with HP Tech Support
(in New Delhi, India) and after (2) "glorious hours" attempting to install
this printer (Step 3 of 4 at 14% I was only at 67Kbs/sec. download time).
I've attempted installing this HP Printer (3) times....uninstall, reboot,
install .... error.....uninstall, reboot....etc.

JUST when I think I've fixed this issue the HP Tech Support tells me that
the download time is TOO SLOW and to stop the installation. After much
troubleshooting he directed me toward the errors page (in the MS Directory)
and stated it was a NETFX.MSI file so......

I went to MicroSoft Website and downloaded this file and I get this error
(below):
=======================
Microsoft .NET Framework 2.0 Setup
Error 25013 failed to install assembly
C:/windows/microsoft.net/framework/v2.0.50727/microsoft.vsa.dll because
strong name signature couldn't be verified. Was the assembly built
delay-signed?
========================

Where does "strong name signature couldn't be verified?" Was the assembly
built delay signed? (I have no idea what this means.

Secondly, I get an Error I get when I tried to install the .Net Framework
2.0 and the reporting details state:
=========================
This error report includes information regarding the condition of
SETUP.exe when the problem occured. The operating system version and
computer hardware in use your digital product ID which could be used to
identify your license and the IP address of your computer.
==================
(OK....what does this mean?)

Is this NET FRAMEWORK (2.0) really necessary to HP OfficeJet 7310 (All in
One) printer?
I've gone to my directory:
C:/windows/microsoft.net/framework
Under my director I see these folders .......
=========================
v1.0.3705
v1.1.4322
v2.0.50727

I see the V2.0.50727 file but because of the error when I've tried to run
the SETUP.exe file for dotnetfx 2.0 (.exe) and I keep getting errors on this.
Your help and assistance would be greatly appreciated.

I should DELETE the v2.0.50727 folder in this directory since it only has
(4) items in it and it didn't complete the install.

I inserted my original WINDOWS XP PRO (CD) and copied the DOTNETFIX on the
desktop but I don't want to run it (yet) because it's only v1.1.4322.573 set
up.
The current verison I have in my folder now is v1.1.4322.

The v1.1.4322.573 set up that I copied from my WINXP Pro CD appears to be
the NEW extension versus the one that's currently in my folder? How could
that be?

I look forward to your diligent assistance in this matter (Soon!).
Thanks!
Bill :)
 
This newsgroup is for the Embedded version of XP, it sounds like you're
having trouble with a printer on the full version of XP; the component
we're talking about in this thread is very different than the version
you're using. You will have better luck finding help with your version
at one of these newsgroups:
- microsoft.public.dotnet.framework
- microsoft.public.windowsxp.general

----
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top