Come On Microsoft! WinPE and MFC 7.0 (.NET) work together

  • Thread starter Thread starter jester
  • Start date Start date
J

jester

Does WinPE support MFC 7.0?

If NOT how do we deploy using sofware built with the new compiler?

If your gonna launch the new technologies you have to support them too:-)

Jester
 
Doesn't MFC 7.0 depend on .Net stuff? It would be hard to do the static
linking with .Net Framework.

Also, I guess that one of the big advantages and purposes of WinPE is that
it is pretty small image. Adding .Net functionality there may force it to
grow dramatically. You may test it with your own "mini" XPe image used for
deployment (haven't tried that, though). Just create a XPe image that will
run on your target hardware, support your network, support tools like
diskpart and etc.. Add .Net (either 1.0 as a component or 1.1 as a separate
install package) and resolve all its dependencies. Then you may see how big
would be the image. If it is acceptable, you may go with this approach -
using your own XPe image for deployment instead of WinPE.

KM

SB> Have you considered to use static linking instead of dynamic?

SB> Regards,
SB> Slobodan

 
Sorry, I don't know what you call MFC 7.0, but I was under impression that
I'm using MFC 7.0 (at least dll's are called that way).

I'm using Microsoft Visual C++ .NET (2002). I have MFC, and I don't use
..NET framework.

I have seen managed code, also I have seen C#, but this is just not me, too
high level for my taste.

Regards,
Slobodan
 
Slobodan,

You're right. MFC 7.0 does not necessarily have dependencies on .Net
Framework.
I was probably under impression that original poster wanted to use some .Net
stuff under WinPE. I must have misread that post :-)

Anyway... WinPE seems to support only 6.0.400 MFC version (6.0.8665.0 build)
and that's what I am using here on my XP Pro and XPe images.

Sorry for any confusions.
KM

SB> Sorry, I don't know what you call MFC 7.0, but I was under
SB> impression that
SB> I'm using MFC 7.0 (at least dll's are called that way).

SB> I'm using Microsoft Visual C++ .NET (2002). I have MFC, and I
SB> don't use .NET framework.

SB> I have seen managed code, also I have seen C#, but this is just not
SB> me, too high level for my taste.

SB> Regards,
SB> Slobodan



SB>>> Have you considered to use static linking instead of dynamic?

SB>>> Regards,
SB>>> Slobodan

 
First thanks for the response.

Slobodan, I am NOT using .NET but I am using MFC 7.0 they don't go
hand in hand. Static linking may be an option I need to think about
it more.

KM how do you know that WinPE does not work with MFC 7.0 This is what
I am trying to deduce - seams like a simple question

Where are the Microsoft folks?

Jester
 
jester,

I've checked WinPE CD (\I386\SYSTEM32 dir) and found only MFC 6.0.400
binaries.

KM

j> First thanks for the response.

j> Slobodan, I am NOT using .NET but I am using MFC 7.0 they don't go
j> hand in hand. Static linking may be an option I need to think about
j> it more.

j> KM how do you know that WinPE does not work with MFC 7.0 This is what
j> I am trying to deduce - seams like a simple question

j> Where are the Microsoft folks?

j> Jester


SB>>> Sorry, I don't know what you call MFC 7.0, but I was under
SB>>> impression that
SB>>> I'm using MFC 7.0 (at least dll's are called that way).

SB>>> I'm using Microsoft Visual C++ .NET (2002). I have MFC, and I
SB>>> don't use .NET framework.

SB>>> I have seen managed code, also I have seen C#, but this is just
SB>>> not me, too high level for my taste.

SB>>> Regards,
SB>>> Slobodan



SB>>>>> Have you considered to use static linking instead of dynamic?

SB>>>>> Regards,
SB>>>>> Slobodan

 
Jester,

Use dependency walker to see what dll files you need to include in your
program folder, that are missing in WinPE.

Or switch linking from dynamic to static. You need to change in your project
settings only one parameter.

Is this hard to do?
Or you need small program?

Regards,
Slobodan
 
Back
Top