ssms 2014 - Visual Studio 2013 High DPI workaround causes debugger to fail -
similar question visual studio 2013 high dpi on 4k screen had posted answer have removed since uncovering issue below.
i have bought new 4k laptop , have been having problems high dpi display of ssis package designer , dialogs in vs2013 dialogs etc in ssms.
a workaround found ssms enable bitmap scaling , create manifest file - ssms.exe.manifest - in same folder ssms.exe.
this article describes how fix ssms
for completeness, i've duplicated process described in article.
set registry key:
[hkey_local_machine\software\microsoft\windows\currentversion\sidebyside] "preferexternalmanifest"=dword:00000001
and paste xml manifest file.
<?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestversion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3"> <dependency> <dependentassembly> <assemblyidentity type="win32" name="microsoft.windows.common-controls" version="6.0.0.0" processorarchitecture="*" publickeytoken="6595b64144ccf1df" language="*"> </assemblyidentity> </dependentassembly> </dependency> <dependency> <dependentassembly> <assemblyidentity type="win32" name="microsoft.vc90.crt" version="9.0.21022.8" processorarchitecture="amd64" publickeytoken="1fc8b3b9a1e18e3b"> </assemblyidentity> </dependentassembly> </dependency> <trustinfo xmlns="urn:schemas-microsoft-com:asm.v3"> <security> <requestedprivileges> <requestedexecutionlevel level="asinvoker" uiaccess="false"/> </requestedprivileges> </security> </trustinfo> <asmv3:application> <asmv3:windowssettings xmlns="http://schemas.microsoft.com/smi/2005/windowssettings"> <ms_windowssettings:dpiaware xmlns:ms_windowssettings="http://schemas.microsoft.com/smi/2005/windowssettings">false</ms_windowssettings:dpiaware> </asmv3:windowssettings> </asmv3:application> </assembly>
now works great (so far) ssms, tried apply fix vs2013. while fix ssis designer display problem, causes issue when attempting launch debugger. additionally, affecting debugging other project types - c#, vb ssis projects.
i'm guessing dependencies in manifest incomplete or inaccurate, since 0x80040155
com interface not registered error code.
unable start debugging. error occurred indicates corrupt installation (code 0x80040155). if problem persists, repair visual studio installation via 'add or remove programs' in control panel. (microsoft visual studio debugger) unable start debugging. debugger not installed. run setup install or repair debugger. (microsoft.datatransformationservices.vsintegration) ------------------------------ program location: @ microsoft.datatransformationservices.project.datatransformationspackagedebugger.launchvsdebugger(ivsdebugger ivsdebugger, datatransformationsprojectconfigurationoptions options) @ microsoft.datatransformationservices.project.datatransformationspackagedebugger.validateandrundebugger(int32 flags, ioutputwindow outputwindow, datatransformationsprojectconfigurationoptions options) @ microsoft.datatransformationservices.project.datatransformationsprojectdebugger.launchdtspackage(int32 launchoptions, projectitem startupprojitem, datatransformationsprojectconfigurationoptions options) @ microsoft.datatransformationservices.project.datatransformationsprojectdebugger.launchactivepackage(int32 launchoptions) @ microsoft.datatransformationservices.project.datatransformationsprojectdebugger.launchdtspackage(int32 launchoptions, datatransformationsprojectconfigurationoptions options) @ microsoft.datatransformationservices.project.datatransformationsprojectdebugger.launch(int32 launchoptions, datatransformationsprojectconfigurationoptions options) ===================================
so question can suggest suitable manifest vs2013 (or way make ssis designer behave)?
ok, absolutely have no idea i'm doing.
however, in same folder devenv.exe (c:\program files (x86)\microsoft visual studio 12.0\common7\ide), there couple of other manifest files, 1 of debuggerproxy.dll.manifest. since debugger problem , there seemed missing reference debugger, merged content devenv.exe.manifest file , came this, works me:
<?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestversion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3"> <dependency> <dependentassembly> <assemblyidentity type="win32" name="microsoft.windows.common-controls" version="6.0.0.0" processorarchitecture="*" publickeytoken="6595b64144ccf1df" language="*"> </assemblyidentity> </dependentassembly> </dependency> <dependency> <dependentassembly> <assemblyidentity type="win32" name="microsoft.vc90.crt" version="9.0.21022.8" processorarchitecture="amd64" publickeytoken="1fc8b3b9a1e18e3b"> </assemblyidentity> </dependentassembly> </dependency> <trustinfo xmlns="urn:schemas-microsoft-com:asm.v3"> <security> <requestedprivileges> <requestedexecutionlevel level="asinvoker" uiaccess="false"/> </requestedprivileges> </security> </trustinfo> <asmv3:application> <asmv3:windowssettings xmlns="http://schemas.microsoft.com/smi/2005/windowssettings"> <ms_windowssettings:dpiaware xmlns:ms_windowssettings="http://schemas.microsoft.com/smi/2005/windowssettings">false</ms_windowssettings:dpiaware> </asmv3:windowssettings> </asmv3:application> <file name="debuggerproxy.dll"> <comclass clsid="{c5621364-87cc-4731-8947-929cae75323e}" threadingmodel="both"/> </file> <cominterfaceexternalproxystub name="causalityinternal_iad7alcausalityeventbridge" iid="{f6a124d7-5bb7-47b2-a9af-aab0eeab60e3}" nummethods="5" proxystubclsid32="{c5621364-87cc-4731-8947-929cae75323e}"/> <cominterfaceexternalproxystub name="causalityinternal_isdmcausalityeventcallback" iid="{74d108f1-1fd2-4699-991e-c4bad52e773d}" nummethods="4" proxystubclsid32="{c5621364-87cc-4731-8947-929cae75323e}"/> ... many more entries ... </assembly>
unfortunately, there 30k limit on characters post , not fit, stuck copy of file in 1 drive here.
Comments
Post a Comment