Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / Managed C++ / March 2005

Tip: Looking for answers? Try searching our database.

Where is "f:\vs70builds\3077\vc\mfcatl?\ship\atlmfc\..." ?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Old Codger - 22 Mar 2005 15:31 GMT
Thanks for this Oleg, nice try! Unfortunately the solution you gave
refers to .NET 2002 and I am using .NET 2003.

In the article it says:
"This bug was corrected in Microsoft Visual C++ .NET (2003), and all
versions of Microsoft Visual Studio .NET (2003). "

Also, the "SourceFiles" directory DOES exist for VC7.1 and it appears
to contain the correct path.

See if here is something useful:
http://support.microsoft.com/default.aspx?scid=kb;en-us;318367

Regards,
Oleg
Oleg Starodumov - 22 Mar 2005 16:09 GMT
> Thanks for this Oleg, nice try! Unfortunately the solution you gave
> refers to .NET 2002 and I am using .NET 2003.
[quoted text clipped - 5 lines]
> Also, the "SourceFiles" directory DOES exist for VC7.1 and it appears
> to contain the correct path.

OK, then try the following:

1. Make sure that the MFC/ATL source files are installed
(see <VSInstallDir>\vc7\atlmfc\src)

2. Make sure VS.NET knows the path to them
(Tools | Options | Projects | VC++ Directories,
Show directories for -> Source files)

3. Make sure the files are _not_ in the following list in your solution settings:
Solution properties | Common properties | Debug source files | Do not look
for these source files

4. If none of the above helps, manually open the needed file when debugging,
and use R-Click | Go To Source in Disassembly window to ask the debugger
to go to the source.

Regards,
Oleg
Old Codger - 24 Mar 2005 17:41 GMT
Thanks Oleg for your detailed reply. I will look at this and see if it
resolves the problem. I did find some information though which said
that this drive F path is the path on the Microsoft development
machine where the MFC DLLs were originally built.

No, I don't understand it either but apparently it is good for us!

O.C.

> > Thanks for this Oleg, nice try! Unfortunately the solution you gave
> > refers to .NET 2002 and I am using .NET 2003.
[quoted text clipped - 25 lines]
> Regards,
> Oleg
Fuzzier - 26 Mar 2005 16:35 GMT
You may consider re-build atl library yourself.
open a command line console,
change the current directory to "%VS7.0 Install Path%\Vc7\atlmfc\src",
enter "vsvars32.bat" (%VS7.0 Install Path%\Common7\Tools), this should set
the corrent evironment variables for search paths,
enter "nmake -f atlmfc.mak ATL", this will build atl library,
copy the wanted version to atlmfc\lib directory (*.lib, *.pdb), and
%windows%\system32 directory (*.dll).

"Old Codger" <OldCodger101@hotmail.com>
??????:c339d4a6.0503240841.12e1275f@posting.google.com...
> Thanks Oleg for your detailed reply. I will look at this and see if it
> resolves the problem. I did find some information though which said
[quoted text clipped - 37 lines]
>> Regards,
>> Oleg

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.