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

http://www.sqlservercentral.com/blogs/spaghettidba/2015/10/14/ssms-in-high-dpi-displays-how-to-stop-the-madness/

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

Popular posts from this blog

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more