Visual Studio 2012 on Win8 (PCA mitigation)

[NewsArchive]

Just a minor issue, but a funny one (some kind of inside joke). The Setup
system is the first experience most of us have of a program.

The attached screenshot shows a "This program might not have uninstalled
correctly" PCA mitigation under Windows 8. And yes, that's from the brand
new Visual Studio 2012 RTM <g>.

The Program Compatibility Assistant (PCA) is a feature in Windows 8, Windows
7, Windows Server 2008 and Windows Vista which has been designed to detect
compatibility issues in older ("legacy") programs. PCA plays a significant
role in application compatibility in Windows 8. The service displays a
compatibility warning window if compatibility issues have been detected
during de-/installation or program starts. The user usually does have a
choice to continue but programs are sometimes blocked from running as well.
If that happens, users have the option to check online for possible
solutions.

So what happened here? Well, the Visual Studio Setup Team forgot to make
the VS2012 install and uninstall applications "Windows 8 aware" and so PCA
might kick in under certain circumstances. I debugged it and the VS2012
install and uninstall loader applications are only Windows Vista and Windows
7 aware. Remember, this is from the "Visual Studio 2012" system, the
"mother" of all modern Windows 8 applications <g>. That's so cool :-)
Anything can happen in this over-complex IT world.

Of course, the latest SetupBuilder 7.7 install and uninstall applications
are fully Windows 8 aware and you'll never see such a PCA mitigation on
Windows 8 (or any previous UAC-aware Windows operating system).

So just compile your setup with SB77 and you are done and safe.

"SetupBuilder -- simplify the over-complex world of installation." (TM) <g>

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

Helping You Build Better Installations
SetupBuilder "point. click. ship"
Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Are you sure MS did not do that on purpose so their customers could
debug it and discover that mistake? That would cause me to recheck my
work to make sure I did not forget it <vbg>

Seriously, glad you are on top of this. Every time I see this message,
my first thought is *always* "That would not happen if they used
SetupBuilder!" <g>

--

Russ Eggen
RADFusion International, LLC

[NewsArchive]

Friedrich,

> Just a minor issue, but a funny one (some kind of inside joke). The Setup
> system is the first experience most of us have of a program.

Obviously they should be using SB!!!!

We had a long discussion about 8 last night at the UG meeting. I can
say that most have not seen the "Modern UI" and were amazed at what MS
has done... by the way, that was amazement at the poor choice of
changes. Nothing appeared to be a move in the right direction.

Apple releases Retina displays boasting the best graphics interface
while MS back tracks to the flattest, most boring interface they can
imagine... seems a bit at odds. Just a bit!<g>

--
Lee White

RPM Report Viewer.: http://www.cwaddons.com/products/rpm/
RPM Review........: http://www.clarionmag.com/cmag/v11/v11n06rpm.html
Report Faxing.....: http://www.cwaddons.com/products/afe/
---Enroll Today---: http://CWaddons.com

Enhanced Reporting: http://CreativeReporting.com


Product Release & Update Notices
http://twitter.com/DeveloperPLUS