Emerald Editor Discussion
March 25, 2017, 02:53:30 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News:
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Crimson Editor SVN286 and Windows 7  (Read 15181 times)
0 Members and 1 Guest are viewing this topic.
rbon
Miner
**
Posts: 31


« on: August 05, 2010, 10:51:55 am »

Hi,
I have build a version of Crimson Editor for Windows 7 32 bit.
In short I have:
1. install VS 2008
2. install Windows SDK for Windows  7 and .NET Framewordk 3.5 SP1
3. run Windows SDK Configuration Tool for change SDK of VS 2008 (v6.0A) to v7.0 (for Windows 7)
4. changed some setup of VS 2008:
-> Linker - -> Manifest File
.. Enable User Account Control (UAC)  set to  No
.. UAC Execution Level                     remain AsInvoker
.. UAC Bypass UI Protection              set to No
Finally I have build cedt.exe with UAC Bypass UI Protection set to "No" and then another build with "Yes".
Feedback is appreciated.



* cedt_exe_en_win7.zip (550.13 KB - downloaded 548 times.)
* cedt_exe_en_win7_UAC bypass UI.zip (550.13 KB - downloaded 510 times.)
« Last Edit: September 13, 2010, 12:25:46 pm by rbon » Logged
exar
Prospector
*
Posts: 2


« Reply #1 on: August 25, 2010, 03:36:37 am »

Neither of rbon's executables gets rid of the "unknown publisher" dialog box for me. Dragging and dropping still does not work, either. They both work just as well as the SVN286 executable available on sourceforge.

jszpilewski's executable works, but I am assuming it is based on SVN263, since Crimson Editor SVN286 had not yet been released to sourceforce when it was made. I looked at the MSDN thread from which jszpilewski obtained the original information. I didn't read the whole thread, but I did find out how to manipulate embedded executable manifests using the manifest tool that comes with all Visual Studio versions, including the Express editions (i.e., mt.exe).

I was able to export the manifests from the SVN286 executable and jszpilewski's working executable and compare them. I made what looked to be the appropriate changes and replaced the manifest in the SVN286 executable with the modified manifest without having to rebuild. To clarify, I don't see where the following change was made in the manifest embedded in jszpilewski's executable.
Following that I changed:
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
to:
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">

in Manifest.xml
It still references the "asm.v3" namespace, as far as I can tell. The biggest difference I see is in the requestedExecutionLevel tag as follows.
Quote from: manifest embedded in SVN286 executable
<requestedExecutionLevel level="highestAvailable"></requestedExecutionLevel>
Quote from: manifest embedded in jszpilewski's SVN263 executable
<requestedExecutionLevel level="asInvoker" uiAccess="false"></requestedExecutionLevel>

I have attached the "patched" SVN286 executable. It works on my Windows 7 x64 system. Just back up cedt.exe from your original Crimson Editor installation and drop this in as a replacement. I do hope that it works for you, but the important thing is that it works for me. Cheesy

* cedt_win7_exar.zip (556.96 KB - downloaded 599 times.)
Logged
rbon
Miner
**
Posts: 31


« Reply #2 on: August 25, 2010, 09:57:18 am »

Hi exar
thanks for Your feedback.
1. I have browse inside "manifest" file in -> trunk -> res -> manifest
there is the contents of this file:
Code:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <assemblyIdentity version="1.0.0.0" processorArchitecture="X86" name="Microsoft.Windows.CrimsonEditor" type="win32" />
  <description>Crimson Editor</description>
- <dependency>
- <dependentAssembly>
  <assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="X86" publicKeyToken="6595b64144ccf1df" language="*" />
  </dependentAssembly>
  </dependency>
- <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
- <security>
- <requestedPrivileges>
  <requestedExecutionLevel level="highestAvailable" />
  </requestedPrivileges>
  </security>
  </trustInfo>
  </assembly>
also I will change the:
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
to:
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
and
<requestedExecutionLevel level="highestAvailable" />
to
 <requestedExecutionLevel level="AsInvoker" />
2. Linker  User Account Control (UAC)  set to  Yes
3. I will use other hints of jszpilewski
4. my build was for Windows 7 32 bit
5. I use the build svn286 because this version allows the multilanguage.
6. I will try Your build.
Thanks again
« Last Edit: January 04, 2011, 02:11:50 pm by rbon » Logged
exar
Prospector
*
Posts: 2


« Reply #3 on: August 25, 2010, 03:44:31 pm »

also I will change the:
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
to:
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
and
<requestedExecutionLevel level="highestAvailable" />
to
 <requestedExecutionLevel level="AsInvoker" />
I should have been clearer in my original reply. I don't think the namespace version (i.e. asm.v2 versus asm.v3) is the issue, since I was able to stop the prompts on my system without changing it. The only change I made was to the requestedExecutionLevel tag. Here is the modified manifest contained in the executable I attached to my original reply.
Code:
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity version="1.0.0.0" processorArchitecture="X86" name="Microsoft.Windows.CrimsonEditor" type="win32"></assemblyIdentity>
  <description>Crimson Editor</description>
  <dependency>
    <dependentAssembly>
      <assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="X86" publicKeyToken="6595b64144ccf1df" language="*"></assemblyIdentity>
    </dependentAssembly>
  </dependency>
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel level="asInvoker" uiAccess="false"></requestedExecutionLevel>
      </requestedPrivileges>
    </security>
  </trustInfo>
</assembly>
Logged
rbon
Miner
**
Posts: 31


« Reply #4 on: September 12, 2010, 05:10:17 pm »

Hi,
there is the version with a new manifest file:
1. I have take the manifest.xml from svn263 (thanks to exar)
2. I have added the first row from manifest.xml of svn286
I hope that this build work well  Wink

* cedt_exe_en_win7_v2.zip (550.15 KB - downloaded 807 times.)
* manifest.xml_svn286_win7_v1.zip (0.72 KB - downloaded 547 times.)
* cedt_exe_en_win7_v2_full_speed.zip (511.56 KB - downloaded 629 times.)
« Last Edit: September 13, 2010, 12:25:01 pm by rbon » Logged
MidSpeck
Prospector
*
Posts: 1


« Reply #5 on: March 25, 2011, 07:14:44 am »

Are you in essence doing this what is talked about here?
http://the.techy.dstro.com/node/16

It seemed to fix the drag and drop problems for me by not elevating it to admin privileges.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.124 seconds with 18 queries.