Comments for Jochen Kalmbach's Blog http://blog.kalmbach-software.de Infos about Windows development and dotNET Framework Thu, 29 Jul 2010 11:38:49 +0000 http://wordpress.org/?v=2.3.3 Comment on Howto: Deploy VC2008 apps without installing vcredist_x86.exe by jkalmbach http://blog.kalmbach-software.de/2008/05/03/howto-deploy-vc2008-apps-without-installing-vcredist_x86exe/#comment-1224 jkalmbach Thu, 15 Jul 2010 16:56:49 +0000 http://blog.kalmbach-software.de/2008/05/03/howto-deploy-vc2008-apps-without-installing-vcredist_x86exe/#comment-1224 Maybe you have forgott to remove the publicKeyToken? Or you have other DLLs which have a embedded manifest with the publicKeyToken? Maybe you have forgott to remove the publicKeyToken? Or you have other DLLs which have a embedded manifest with the publicKeyToken?

]]> Comment on Howto: Deploy VC2008 apps without installing vcredist_x86.exe by Chronogps http://blog.kalmbach-software.de/2008/05/03/howto-deploy-vc2008-apps-without-installing-vcredist_x86exe/#comment-1223 Chronogps Thu, 15 Jul 2010 16:32:00 +0000 http://blog.kalmbach-software.de/2008/05/03/howto-deploy-vc2008-apps-without-installing-vcredist_x86exe/#comment-1223 I followed the tutorial but I get a 0xC0150002 error (missing DLL I supposed). Any idea ? I followed the tutorial but I get a 0xC0150002 error (missing DLL I supposed). Any idea ?

]]> Comment on $log$ substitution check-in policy published by jkalmbach http://blog.kalmbach-software.de/2009/08/08/log-substitution-check-in-policy-published/#comment-1221 jkalmbach Fri, 09 Jul 2010 11:12:33 +0000 http://blog.kalmbach-software.de/2009/08/08/log-substitution-check-in-policy-published/#comment-1221 The "$log$ entry is incorrect; even if it seems to be correct. In some scenarious, it might lead to the wrong changeset (if two people check-in almost at the same time, then one $log$ entry will be wrong. The “$log$ entry is incorrect; even if it seems to be correct.
In some scenarious, it might lead to the wrong changeset (if two people check-in almost at the same time, then one $log$ entry will be wrong.

]]> Comment on $log$ substitution check-in policy published by czar http://blog.kalmbach-software.de/2009/08/08/log-substitution-check-in-policy-published/#comment-1220 czar Wed, 07 Jul 2010 21:36:27 +0000 http://blog.kalmbach-software.de/2009/08/08/log-substitution-check-in-policy-published/#comment-1220 fabulous feature by the way. we need this so files get tagged and marked with our developer comments, before we hand them to a client. thank you! fabulous feature by the way. we need this so files get tagged and marked with our developer comments, before we hand them to a client. thank you!

]]> Comment on $log$ substitution check-in policy published by czar http://blog.kalmbach-software.de/2009/08/08/log-substitution-check-in-policy-published/#comment-1219 czar Wed, 07 Jul 2010 21:27:46 +0000 http://blog.kalmbach-software.de/2009/08/08/log-substitution-check-in-policy-published/#comment-1219 Interesting, since $log$ is showing the correct changeset# without using quote "+1". Personally, I prefer how $log$ does not show "+1". I thought maybe you improved that feature in a later release, updating $log$ but not $revision$ (since the behavior is different between the two). Here is how my file (changeset 3799 after check-in). You can see $revision is 3789+1 whereas $log$ shows 'revision 3799'. * $Revision: 3798+1 $ * $log$ * Revision 3799... Interesting, since $log$ is showing the correct changeset# without using quote “+1″. Personally, I prefer how $log$ does not show “+1″. I thought maybe you improved that feature in a later release, updating $log$ but not $revision$ (since the behavior is different between the two).

Here is how my file (changeset 3799 after check-in). You can see $revision is 3789+1 whereas $log$ shows ‘revision 3799′.

* $Revision: 3798+1 $
* $log$
* Revision 3799…

]]> Comment on $log$ substitution check-in policy published by jkalmbach http://blog.kalmbach-software.de/2009/08/08/log-substitution-check-in-policy-published/#comment-1218 jkalmbach Wed, 07 Jul 2010 21:08:54 +0000 http://blog.kalmbach-software.de/2009/08/08/log-substitution-check-in-policy-published/#comment-1218 The default log-pattern just adds "+1" to the last changeset. So to be correct: The log-entry should also have been the format "{6}+1" instead of "{7}"... The default log-pattern just adds “+1″ to the last changeset.
So to be correct: The log-entry should also have been the format “{6}+1″ instead of “{7}”…

]]> Comment on $log$ substitution check-in policy published by czar http://blog.kalmbach-software.de/2009/08/08/log-substitution-check-in-policy-published/#comment-1217 czar Wed, 07 Jul 2010 21:02:36 +0000 http://blog.kalmbach-software.de/2009/08/08/log-substitution-check-in-policy-published/#comment-1217 I read the doc explaining why the current revision# is not available (code runs prior to check-in), however $log$ appears to show the correct value. Why does $log$ show the correct revision number, but $revision$ uses "+1"? here's an example: * $Revision: 3798+1 $ * $log$ * Revision 3799 2010/07/07 13:12:39 czar * testing checkin only I read the doc explaining why the current revision# is not available (code runs prior to check-in), however $log$ appears to show the correct value. Why does $log$ show the correct revision number, but $revision$ uses “+1″?

here’s an example:

* $Revision: 3798+1 $
* $log$
* Revision 3799 2010/07/07 13:12:39 czar
* testing checkin only

]]> Comment on Deployment of VC2008 apps without installing anything by Articles about _bind_to_current_vclibs_version 1 volume 2 « Article Directory http://blog.kalmbach-software.de/2009/05/27/deployment-of-vc2008-apps-without-installing-anything/#comment-1203 Articles about _bind_to_current_vclibs_version 1 volume 2 « Article Directory Sat, 12 Jun 2010 14:01:57 +0000 http://blog.kalmbach-software.de/2009/05/27/deployment-of-vc2008-apps-without-installing-anything/#comment-1203 [...] Jochen Kalmbach’s Blog ” Blog Archive ” Deployment of VC2008 … The problem is that by default VC2008 uses the DLL-version of the CRT/MFC. … #define _BIND_TO_CURRENT_VCLIBS_VERSION 1. in stdafx.h (at the top) or in your project … [...] […] Jochen Kalmbach’s Blog ” Blog Archive ” Deployment of VC2008 … The problem is that by default VC2008 uses the DLL-version of the CRT/MFC. … #define _BIND_TO_CURRENT_VCLIBS_VERSION 1. in stdafx.h (at the top) or in your project … […]

]]> Comment on Howto: Deploy VC2008 apps without installing vcredist_x86.exe by Jochen Kalmbach’s Blog » Blog Archive » Deployment of VC2008 apps without installing anything http://blog.kalmbach-software.de/2008/05/03/howto-deploy-vc2008-apps-without-installing-vcredist_x86exe/#comment-1143 Jochen Kalmbach’s Blog » Blog Archive » Deployment of VC2008 apps without installing anything Mon, 10 May 2010 09:00:59 +0000 http://blog.kalmbach-software.de/2008/05/03/howto-deploy-vc2008-apps-without-installing-vcredist_x86exe/#comment-1143 [...] Just a small note: You should be aware, that this “AppLocal” installation is not really “AppLocal”… it is only AppLocal, if the vcredist_*.exe was not installed. If the vcredist_*.exe is installed, then the DLLs from the WinSxS directory will be used. If you want to prevent this, you can do a really AppLocal deployment. [...] […] Just a small note: You should be aware, that this “AppLocal” installation is not really “AppLocal”… it is only AppLocal, if the vcredist_*.exe was not installed. If the vcredist_*.exe is installed, then the DLLs from the WinSxS directory will be used. If you want to prevent this, you can do a really AppLocal deployment. […]

]]> Comment on Supported runtime OS for VC2010 by Gideon7 http://blog.kalmbach-software.de/2010/04/22/supported-runtime-os-for-vc2010/#comment-1113 Gideon7 Thu, 29 Apr 2010 00:28:15 +0000 http://blog.kalmbach-software.de/2010/04/22/supported-runtime-os-for-vc2010/#comment-1113 The fix for Windows 2000 is pretty simple. Create a .LIB that implements the missing functionality and link it ahead of KERNEL32.LIB. You will need to use the linker option /NODEFAULTLIB:kernel32.lib so that you can put your w2kcompat.lib ahead of kernel32.lib. The fix for Windows 2000 is pretty simple. Create a .LIB that implements the missing functionality and link it ahead of KERNEL32.LIB.

You will need to use the linker option /NODEFAULTLIB:kernel32.lib so that you can put your w2kcompat.lib ahead of kernel32.lib.

]]> Comment on Howto: Deploy VC2008 apps without installing vcredist_x86.exe by jkalmbach http://blog.kalmbach-software.de/2008/05/03/howto-deploy-vc2008-apps-without-installing-vcredist_x86exe/#comment-1053 jkalmbach Fri, 16 Apr 2010 16:24:48 +0000 http://blog.kalmbach-software.de/2008/05/03/howto-deploy-vc2008-apps-without-installing-vcredist_x86exe/#comment-1053 You have some kind of "bug" in one of your dependencies... you must not deploy debug versions! You have some kind of “bug” in one of your dependencies… you must not deploy debug versions!

]]> Comment on Howto: Deploy VC2008 apps without installing vcredist_x86.exe by Bruno http://blog.kalmbach-software.de/2008/05/03/howto-deploy-vc2008-apps-without-installing-vcredist_x86exe/#comment-1052 Bruno Fri, 16 Apr 2010 15:40:33 +0000 http://blog.kalmbach-software.de/2008/05/03/howto-deploy-vc2008-apps-without-installing-vcredist_x86exe/#comment-1052 Hey, Sorry for this second message. I also noticed that my manifest file is looking for Microsoft.VC80.CRT & Microsoft.VC90.DebugCRT: I could find VC90.DebugCRT in (ProgramFiles\Microsoft Visual Studio 9.0\VC\redist\Debug_NonRedis\x86) the Visual Studio folder (VS 2008 Professional Edition) but I cannot find the VC80. Can anybody tell me what should I do??? Thanks, Bruno Hey,

Sorry for this second message. I also noticed that my manifest file is looking for Microsoft.VC80.CRT & Microsoft.VC90.DebugCRT:

I could find VC90.DebugCRT in (ProgramFiles\Microsoft Visual Studio 9.0\VC\redist\Debug_NonRedis\x86) the Visual Studio folder (VS 2008 Professional Edition) but I cannot find the VC80. Can anybody tell me what should I do???

Thanks,

Bruno

]]> Comment on Howto: Deploy VC2008 apps without installing vcredist_x86.exe by jkalmbach http://blog.kalmbach-software.de/2008/05/03/howto-deploy-vc2008-apps-without-installing-vcredist_x86exe/#comment-1051 jkalmbach Fri, 16 Apr 2010 15:23:08 +0000 http://blog.kalmbach-software.de/2008/05/03/howto-deploy-vc2008-apps-without-installing-vcredist_x86exe/#comment-1051 If you want an external manifest, you need to disable the embedding of the manifest. See Manifest options (Project-Properties|Manifest Tool|Input and Output|Embed Manifest: No) If you want an external manifest, you need to disable the embedding of the manifest. See Manifest options (Project-Properties|Manifest Tool|Input and Output|Embed Manifest: No)

]]> Comment on Howto: Deploy VC2008 apps without installing vcredist_x86.exe by Bruno http://blog.kalmbach-software.de/2008/05/03/howto-deploy-vc2008-apps-without-installing-vcredist_x86exe/#comment-1050 Bruno Fri, 16 Apr 2010 15:20:38 +0000 http://blog.kalmbach-software.de/2008/05/03/howto-deploy-vc2008-apps-without-installing-vcredist_x86exe/#comment-1050 Hi everybody, I am trying to solve this problem but I have a question. Where do I find the external manifest of my project? When I went to the Debug folder all I can find is app.exe.embed.manifest and app.exe.intermediate.manifest??? Or should I just create it myself??? Thanks, Bruno Hi everybody,

I am trying to solve this problem but I have a question. Where do I find the external manifest of my project? When I went to the Debug folder all I can find is app.exe.embed.manifest and app.exe.intermediate.manifest??? Or should I just create it myself???
Thanks,

Bruno

]]> Comment on Unhandled exceptions in VC8 and above… for x86 and x64 by 处理VS2005（VC8）无法捕获的Unhandled exceptions http://blog.kalmbach-software.de/2008/04/02/unhandled-exceptions-in-vc8-and-above-for-x86-and-x64/#comment-1018 处理VS2005（VC8）无法捕获的Unhandled exceptions Sat, 10 Apr 2010 14:54:02 +0000 http://blog.kalmbach-software.de/2008/04/02/unhandled-exceptions-in-vc8-and-above-for-x86-and-x64/#comment-1018 [...] Unhandled exceptions in VC8 and above… for x86 and x64  [...] […] Unhandled exceptions in VC8 and above… for x86 and x64  […]

]]> Comment on Better sos.dll for debugging in WinDbg available! by First Look at Psscor2 the new WinDBG Debugging Extension for Managed Code - Cory Foy, LLC - Agile Training and Consulting - Enterprise Agility Redefined http://blog.kalmbach-software.de/2010/03/30/better-sosdll-for-debugging-in-windbg-available/#comment-1014 First Look at Psscor2 the new WinDBG Debugging Extension for Managed Code - Cory Foy, LLC - Agile Training and Consulting - Enterprise Agility Redefined Thu, 08 Apr 2010 14:30:15 +0000 http://blog.kalmbach-software.de/2010/03/30/better-sosdll-for-debugging-in-windbg-available/#comment-1014 [...] of what is going on with your managed code. While there are several articles listing out the commands and a detailed command help view, there isn’t much [...] […] of what is going on with your managed code. While there are several articles listing out the commands and a detailed command help view, there isn’t much […]

]]> Comment on Writing MiniDumps in C# by Jochen Kalmbach’s Blog » Blog Archive » Better sos.dll for debugging in WinDbg available! http://blog.kalmbach-software.de/2008/12/13/writing-minidumps-in-c/#comment-994 Jochen Kalmbach’s Blog » Blog Archive » Better sos.dll for debugging in WinDbg available! Tue, 30 Mar 2010 12:47:00 +0000 http://blog.kalmbach-software.de/2008/12/13/writing-minidumps-in-c/#comment-994 [...] Also it has a good “!Analysis” command for dump-files. [...] […] Also it has a good “!Analysis” command for dump-files. […]

]]> Comment on Feedback for VC++ for the version AFTER VS2010 by WinWear http://blog.kalmbach-software.de/2010/03/22/feedback-for-vc-for-the-version-after-vs2010/#comment-960 WinWear Tue, 23 Mar 2010 08:16:14 +0000 http://blog.kalmbach-software.de/2010/03/22/feedback-for-vc-for-the-version-after-vs2010/#comment-960 Interesting information. Maybe they still need some features for the release next year. ;-) Interesting information. Maybe they still need some features for the release next year. ;-)

]]> Comment on Forums NntpBridge and DateTime by jkalmbach http://blog.kalmbach-software.de/2010/03/02/forums-nntpbridge-an-datetime/#comment-885 jkalmbach Thu, 11 Mar 2010 21:19:40 +0000 http://blog.kalmbach-software.de/2010/03/02/forums-nntpbridge-an-datetime/#comment-885 Microsoft has now created a hotfix with my code ;) You can download it from: https://connect.microsoft.com/MicrosoftForums/Downloads Direct-Link: https://connect.microsoft.com/MicrosoftForums/Downloads/DownloadDetails.aspx?DownloadID=27231 Microsoft has now created a hotfix with my code ;)

You can download it from:
https://connect.microsoft.com/MicrosoftForums/Downloads

Direct-Link:
https://connect.microsoft.com/MicrosoftForums/Downloads/DownloadDetails.aspx?DownloadID=27231

]]> Comment on Forums NntpBridge and DateTime by Hermann Hippen http://blog.kalmbach-software.de/2010/03/02/forums-nntpbridge-an-datetime/#comment-872 Hermann Hippen Tue, 09 Mar 2010 23:37:58 +0000 http://blog.kalmbach-software.de/2010/03/02/forums-nntpbridge-an-datetime/#comment-872 Nice find. Good job. Works fine. Thanks a lot. :-) Nice find. Good job. Works fine. Thanks a lot. :-)

]]>