This item is not eligible for Amazon Prime, but millions of other items are. Join Amazon Prime today. Already a member? Sign in.

25 used & new from $5.97
See All Buying Options

Have one to sell? Sell yours here
 
   
Tell a Friend
Visual C++(r).NET Developer's Guide
 
 
Are You an Author or Publisher?
Find out how to publish your own Kindle Books
 
  
Visual C++(r).NET Developer's Guide (Paperback)
by John Mueller (Author) "Many developers see Visual C++ as the old shoe of the programming trade-it feels comfortable and they know it well..." (more)
Key Phrases: public static valuetype, valid configuration names, solution filename, Active Directory, Visual Basic, Sngl Doc (more...)
  3.7 out of 5 stars 7 customer reviews (7 customer reviews)  


Available from these sellers.


25 used & new available from $5.97

Customers Who Bought This Item Also Bought

Microsoft  Visual C++  .NET Step by Step--Version 2003 (Step By Step (Microsoft))

Microsoft Visual C++ .NET Step by Step--Version 2003 (Step By Step (Microsoft)) by Julian Templeman

3.2 out of 5 stars (24)  $26.39
Microsoft Visual C++ .NET 2003 Kick Start

Microsoft Visual C++ .NET 2003 Kick Start by Kate Gregory

4.8 out of 5 stars (6)  $23.09
Explore similar items : Books (2)

Editorial Reviews
Book Description
This is the hard-core resource for serious developers. Coverage includes ADO, ADO+, Acrive Directory, Security, trheads, attributed programming, ATL, web forms, and a complete overview of integration with the .NET platform.

From the Back Cover

Engineer Your Way to Excellence

Maximize the capabilities of Visual C++ .NET using the advanced development strategies presented in this professional resource. Inside, you'll find full details on using threads and graphics, working within the .NET Framework, handling database integration, ensuring security, creating administrative tools, and much more. Build and deploy robust Visual C++ .NET applications that take full advantage of the innovative features of this powerful development tool.

On the CD-ROM:



See all Editorial Reviews

Product Details
  • Paperback: 880 pages
  • Publisher: Osborne/McGraw-Hill; Pap/Cdr edition (January 10, 2002)
  • Language: English
  • ISBN-10: 0072132817
  • ISBN-13: 978-0072132816
  • Product Dimensions: 9.1 x 7.4 x 1.8 inches
  • Shipping Weight: 3.3 pounds
  • Average Customer Review: 3.7 out of 5 stars 7 customer reviews (7 customer reviews)
  • Amazon.com Sales Rank: #1,151,472 in Books (See Bestsellers in Books)
    (Publishers and authors: Improve Your Sales)
  •  Would you like to update product info or give feedback on images? (We'll ask you to sign in so we can get back to you)


John Paul Mueller's latest blog posts
       
 
John Paul Mueller sent the following posts to customers who purchased Visual C++(r).NET Developer's Guide
 
7:57 AM PST, November 15, 2006
This is an amazing business.  It's not hard to find horror stories of all shapes and sizes when it comes to application development.  Things that should work, often don't.  I can truthfully say that I learn something new every day.  In 20 years of writing books, I have never had a day where some new fact didn't slap me in the face.  These new facts are part of the reason I've stayed in this business so long; there is always something interesting to learn, something new to discover.

One of the problems that I recently encountered was in helping someone move code from my machine to their machine.  It seems like it should be an easy task.  Simply pack up the code and move it to the other machine; right?  Actually, no.  Visual Studio .NET doesn't make things that easy.

The first problem that you'll encounter is that Visual Studio .NET embeds the relative and absolute paths to just about everything in the source code files.  Unfortunately, you won't find this information in just one file; the embedded paths appear in the SLN and CONFIG files as a minimum, but you might find them elsewhere as well.

The second problem is that even when you fix the paths in the files, you also have this little problem with references.  They don't work and sometimes refreshing the reference doesn't help.  Generally speaking, you need to recreate all of the references to ensure that they work properly.  Otherwise, you get really strange errors such as one where Visual Studio no longer recognizes things like the Int32 data type.

A third problem occurs when the testing environment varies between two machines. I normally do all of my testing on the local machine, which means that I check the source code out of the server, do any updates, test, and then check the code back into the server.  I normally check the result with a browser afterward so I can see the user-view of things.  Problems arise when the person who receives the code tries to do everything on the server.  For example, you might encounter a problem where a UNC share isn't supported on Windows XP (see Knowledge Base article 810886 for details). Testing locally is always the best idea unless you really do want to set up a remote testing environment.

So, what problems have you run into moving code from one machine to another?  Let me know at JPMAmazon@yahoo.com.
 
Comment    

2:07 PM PDT, August 11, 2006
Microsoft has decided to make life interesting for anyone using Vista by moving the user folders around. Sure, they've creating links for the old folder locations and these links normally work fine, but the fact of the matter is that they sometimes don't with older applications and that can cause problems when you don't know how to handle the situation.

Hard coding folder locations in an application has always been bad practice and this recent move by Microsoft shows just how bad it can be. Personally, I feel the new folder setup has a number of advantages, not the least of which is that the names make a lot more sense and are easy to include in scripts. The new names don't really affect me one way or the other, but I"m sure that Microsoft's goal is to make the folder names easier for people to understand. You can read more about my new view of Vista folders on DevSource.

Of course, I'd like to get your feelings on the matter too. If you're using Vista today, check out the article and then check out your hard drive. You may not have even seen the change until I just mentioned it, which means that the change is a non-issue for you. However, if you have run across problems, let me know about them at JPMAmazon@yahoo.com.
 
Comment    

4:08 PM PDT, August 2, 2006
Sometimes it's interesting to see what you can accomplish with a given tool. Now, I'm all for expanding legtimate uses of a tool, but if I try something out and find it cumbersome, I certainly don't keep trying to perform the task with that tool. For example, I know people who might try to use a spreadsheet as a word processor. Sure, you can do it, but I know far less painful ways of typing a letter. That's why I thought it was so interesting that I was able to devise a method for creating Firefox extensions using Visual Studio.

Visual Studio is an excellent project organization tool, even when you don't use the predefined Microsoft templates. The editor provides all of the color coding you need to create a Firefox extension and you can even reasonably expect the IDE to help you write the code (as odd as that might sound). You can read more about my Firefox extension coding experience on DevSource. What other uses of Visual Studio have you tried? Contact me at JPMAmazon@yahoo.com with your experiences.
 
Comment