Everything you wanted to know about VC++ deployment but were afraid to ask
- Posted: Jan 02, 2008 at 11:32 AM
- 23,277 Views
- 20 Comments
Download
How do I download the videos?
- To download, right click the file type you would like and pick “Save target as…” or “Save link as…”
Why should I download videos from Channel9?
- It's an easy way to save the videos you like locally.
- You can save the videos in order to watch them offline.
- If all you want is to hear the audio, you can download the MP3!
Which version should I choose?
- If you want to view the video on your PC, Xbox or Media Center, download the High Quality WMV file (this is the highest quality version we have available).
- If you'd like a lower bitrate version, to reduce the download time or cost, then choose the Medium Quality WMV file.
- If you have a Zune, WP7, iPhone, iPad, or iPod device, choose the low or medium MP4 file.
- If you just want to hear the audio of the video, choose the MP3 file.
Right click “Save as…”
- Mid Quality WMV (Lo-band, Mobile)
- MP3 (Audio only)
- WMV (WMV Video)
After C++ code has been written, compiled and tested it's now time for figuring out how to deploy it successfully on n number of users' machines and their various configurations... This is no easy task given the number of potential versioning conflicts.
Of course, there are ways to do this, many of them automatic in nature, but which way is the best way? How do the various methodologies of delploying exes and dlls on machines stack up? How does it all work? Deployment is one of those things that many of us
take for granted, but George Mileka and Ben Anderson of the Visual C++ team spend much of their time thinking about the process of deploying code to any number of machines so we don't have to. Tune in and learn about the nitty gritty of VC deployment. There
is plenty of whiteboarding in this one so be sure to put your propeller caps on.
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
Thanks anyway
Interesting point of view. I don't agree, however. Follow these guidelines! They will save you from much grief...
C
I do that Charles whenever is possible, but I was not talking about me.
Most of the software industry "big-names" (not to mention 99% of shareware vendors), ignore these guidelines when designing their products deployment.
(SXS will likely join the registry and UAC in the legendary "it sounded good on paper" pile.)
Wow you must be a busy guy working with so many companies to make such generalizations. So do you hop companies every week. Or are you making something up to have a point. I vote for the latter.
Do they link everything in the binaries? How are updates taken care of in that case?
so in theory MacOS can still suffer from dll hell unless the library directory stores multiple versions of the Library.
Douglash
Well, it does not look substantially different from Windows...
No, I'm not a "busy guy working with many companies". I'm just a regular tech guy who has deployed hundreds of commercial applications during my life. Do you think it's too difficult to recognize a messed up installation?
sry, its been getting on my nerves since channel9 switched players. I appreciate your efforts.
Are you running the lastest Version: 1.0.21115.0?
Linux systems (I believe it's also in most *nix systems) store the dynamic link libraries in /lib and /usr/lib. with .so(dynamic-linked) or .a(static-linked) in extension.
And they put the version number at the end of the file. Then provide symbolic link to the filename without version in extension as the current version.
======
So you'll see:
libsomething.so -> libsomething.so.4.3.3
libsomething.so.3 -> libsomething.so.3.1.0
libsomething.so.4 -> libsomething.so.4.3.3
libsomething.so.3.1.0
libsomething.so.4.3.1
libsomething.so.4.3.3
In some system that doesn't use package management systems.
======
Note that on most systems, some of these libraries are left behind intensionally for backward compatibility reasons. (e.g.: the *-compat packages)
If you install an application that requires previous version of glibc runtime, just install the current version of glibc-compat and you'll get all the previous versions of glibc-runtime. That's how they solve the DLL hell problem.
You can op out... Go to your profile -> settings and disable silverlight for the player.
-Ben
TA.
Remove this comment
Remove this thread
close