MFC6 in Visual Studio.NET
-
Hi, I'm working on a rather huge project, and we would like to start using Visual Studio.NET in the near future. However, we will not be using MFC7 in the next few months; we'd like to stick with MFC6. Is it possible to work in VS.Net while developing with a previous libraryversion? -- Alex Marbus www.marbus.net But then again, I could be wrong.
-
Hi, I'm working on a rather huge project, and we would like to start using Visual Studio.NET in the near future. However, we will not be using MFC7 in the next few months; we'd like to stick with MFC6. Is it possible to work in VS.Net while developing with a previous libraryversion? -- Alex Marbus www.marbus.net But then again, I could be wrong.
AlexMarbus wrote: Is it possible to work in VS.Net while developing with a previous libraryversion? No,You have to use MFC7 there but if you delevop half of your project with MFC6 then you want to swicth to MFC7(VC.NET),there is no problem and you can proceed your project with new version. Mazy "The path you tread is narrow and the drop is shear and very high, The ravens all are watching from a vantage point near by, Apprehension creeping like a choo-train uo your spine, Will the tightrope reach the end;will the final cuplet rhyme?"Cymbaline-Pink Floyd
-
AlexMarbus wrote: Is it possible to work in VS.Net while developing with a previous libraryversion? No,You have to use MFC7 there but if you delevop half of your project with MFC6 then you want to swicth to MFC7(VC.NET),there is no problem and you can proceed your project with new version. Mazy "The path you tread is narrow and the drop is shear and very high, The ravens all are watching from a vantage point near by, Apprehension creeping like a choo-train uo your spine, Will the tightrope reach the end;will the final cuplet rhyme?"Cymbaline-Pink Floyd
Are you sure about that? I have opened my project in VS.Net and MFC7, but there are a lot of things different in MFC7, compared to MFC6. I get a lot of compile-errors I didn't get with MFC6. So, I can understand that MFC7 will behave very differently compared to MFC6. I have figured out that I can tell VS.Net to use different folders for include and sourcefiles, so it will include MFC6 files, however I can't manage to tell the linker it should link with MFC42.dll instead of MFC70.dll. I really hoped I could use MFC6 in VS.NET because I don't feel very much like testing the entire project (which is rather huge) to see on what points it differs from the previous library. -- Alex Marbus www.marbus.net But then again, I could be wrong.
-
Are you sure about that? I have opened my project in VS.Net and MFC7, but there are a lot of things different in MFC7, compared to MFC6. I get a lot of compile-errors I didn't get with MFC6. So, I can understand that MFC7 will behave very differently compared to MFC6. I have figured out that I can tell VS.Net to use different folders for include and sourcefiles, so it will include MFC6 files, however I can't manage to tell the linker it should link with MFC42.dll instead of MFC70.dll. I really hoped I could use MFC6 in VS.NET because I don't feel very much like testing the entire project (which is rather huge) to see on what points it differs from the previous library. -- Alex Marbus www.marbus.net But then again, I could be wrong.
AlexMarbus wrote: I get a lot of compile-errors I didn't get with MFC6. This is VERY strange,What was those errors? I used my MFC6 projects in VC.NET and there were no error also I saw thousends times in this forum there is no problem for that. AlexMarbus wrote: I really hoped I could use MFC6 in VS.NET because I don't feel very much like testing the entire project (which is rather huge) to see on what points it differs from the previous library. I think you'd better not to take risk (because of those errors)and still use previous version of VC unless someone make sure for it. Maybe other guys here can give you more information and of course help you better than me. :) Mazy "The path you tread is narrow and the drop is shear and very high, The ravens all are watching from a vantage point near by, Apprehension creeping like a choo-train uo your spine, Will the tightrope reach the end;will the final cuplet rhyme?"Cymbaline-Pink Floyd
-
AlexMarbus wrote: I get a lot of compile-errors I didn't get with MFC6. This is VERY strange,What was those errors? I used my MFC6 projects in VC.NET and there were no error also I saw thousends times in this forum there is no problem for that. AlexMarbus wrote: I really hoped I could use MFC6 in VS.NET because I don't feel very much like testing the entire project (which is rather huge) to see on what points it differs from the previous library. I think you'd better not to take risk (because of those errors)and still use previous version of VC unless someone make sure for it. Maybe other guys here can give you more information and of course help you better than me. :) Mazy "The path you tread is narrow and the drop is shear and very high, The ravens all are watching from a vantage point near by, Apprehension creeping like a choo-train uo your spine, Will the tightrope reach the end;will the final cuplet rhyme?"Cymbaline-Pink Floyd
Mazdak wrote: This is VERY strange,What was those errors? I used my MFC6 projects in VC.NET and there were no error also I saw thousends times in this forum there is no problem for that. Most compile-errors were related to RichEdit, e.g. a wordbreakproc. But there were some errors related to CString as well. (Has that class moved to ATL?) Mazdak wrote: I think you'd better not to take risk (because of those errors)and still use previous version of VC unless someone make sure for it. Maybe you're right, but I wanted my colleagues to get used to the look and feel of VS.Net in the first stage, and one stage later move the entire project up to MFC7. Mazdak wrote: Maybe other guys here can give you more information and of course help you better than me You have been a big help so far, thanks for that! -- Alex Marbus www.marbus.net But then again, I could be wrong.
-
Mazdak wrote: This is VERY strange,What was those errors? I used my MFC6 projects in VC.NET and there were no error also I saw thousends times in this forum there is no problem for that. Most compile-errors were related to RichEdit, e.g. a wordbreakproc. But there were some errors related to CString as well. (Has that class moved to ATL?) Mazdak wrote: I think you'd better not to take risk (because of those errors)and still use previous version of VC unless someone make sure for it. Maybe you're right, but I wanted my colleagues to get used to the look and feel of VS.Net in the first stage, and one stage later move the entire project up to MFC7. Mazdak wrote: Maybe other guys here can give you more information and of course help you better than me You have been a big help so far, thanks for that! -- Alex Marbus www.marbus.net But then again, I could be wrong.
AlexMarbus wrote: Most compile-errors were related to RichEdit, e.g In VC.7 there is new class for richedit.Go to dialog editor.You'll see "Rich Edit 2.0 Control",this one is for new version. AlexMarbus wrote: But there were some errors related to CString as well. (Has that class moved to ATL?) Not move to ATL,it share with ATL.In MFC6 there where no base class for CString,but here there is CSimpleString that CString derive from that,and there are some additional function here for CString. Now I can see there are some changes. ;) But I never had any problem with my old CString when I migrate from MFC6 to MFC7. :) AlexMarbus wrote: You have been a big help so far, thanks for that! Thank you Alex. :):-O :-O :-O :-O Mazy "The path you tread is narrow and the drop is shear and very high, The ravens all are watching from a vantage point near by, Apprehension creeping like a choo-train uo your spine, Will the tightrope reach the end;will the final cuplet rhyme?"Cymbaline-Pink Floyd
-
AlexMarbus wrote: Most compile-errors were related to RichEdit, e.g In VC.7 there is new class for richedit.Go to dialog editor.You'll see "Rich Edit 2.0 Control",this one is for new version. AlexMarbus wrote: But there were some errors related to CString as well. (Has that class moved to ATL?) Not move to ATL,it share with ATL.In MFC6 there where no base class for CString,but here there is CSimpleString that CString derive from that,and there are some additional function here for CString. Now I can see there are some changes. ;) But I never had any problem with my old CString when I migrate from MFC6 to MFC7. :) AlexMarbus wrote: You have been a big help so far, thanks for that! Thank you Alex. :):-O :-O :-O :-O Mazy "The path you tread is narrow and the drop is shear and very high, The ravens all are watching from a vantage point near by, Apprehension creeping like a choo-train uo your spine, Will the tightrope reach the end;will the final cuplet rhyme?"Cymbaline-Pink Floyd
Mazdak wrote: In VC.7 there is new class for richedit.Go to dialog editor.You'll see "Rich Edit 2.0 Control",this one is for new version. I create several CRichEditCtrl's (3.0) dynamically, it's not limited to a dialog: I place them on a a CxxView. But thanks again :) -- Alex Marbus www.marbus.net But then again, I could be wrong.