Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Adobe SVG Viewer won't load in .NET browser control on a Windows 7 64bit OS

Posted on 2010-09-13
4
Medium Priority
?
2,424 Views
Last Modified: 2013-11-29
I have a VB.NET windows application running on the 64bit version of Windows 7 that utilizes a
browser control. The browser control loads a page which uses the Adobe SVG viewer to load
a GIS map. The control works fine when loaded directly in the 32bit version of IE but when I try
to load the SVG viewer within the browser contol I only get the outline of the map with a red X in
top left corner.

It's well known that the Adobe SVG viewer is not supported by the 64bit version of IE8. Is there
any way to force the browser control to use the 32bit version of IE rather than the 64 bit? I would
like to continue to use the browser control as it works fine on any of the 32bit Windows systems
we have the application deployed on. The issues is with the Adobe SVG viewer loading in the
browser control on the Windows 7 64bit systems.

Any help would be greatly appreciated!
0
Comment
Question by:CaptainCrunch7777
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 19

Expert Comment

by:Rimvis
ID: 33805890
Hi CaptainCrunch7777, Check compilation settings for your app. If it is set to "Any CPU", try to use "x86". Maybe this way browser control will load 32-bit IE.
0
 

Author Comment

by:CaptainCrunch7777
ID: 33808683
Hi Sage,

I've tried that but the app will always load the 64 bit version of IE no matter which CPU it's compiled for.
0
 

Accepted Solution

by:
CaptainCrunch7777 earned 0 total points
ID: 33808725
I have solved the issue. It was the Windows Data Execution Prevention that was preventing the viewer from loading in the browser control. To disable DEP in the EXE you need to do the following:

Go to Project Properties -> Compile -> Build Events

Paste the following under post-build:

call "$(DevEnvDir)..\tools\vsvars32.bat"
editbin.exe /NXCOMPAT:NO "$(TargetPath)"

When creating the install package, use the EXE from the obj\Release folder rather than the bin\Release folder, so I had to add another post-build line to patch that one too
0
 

Expert Comment

by:Cut_OS
ID: 33842376
Good solution, thank you so much!
A better way: Go to the project-linker-settings and add under command-line options:

/NXCOMPAT:NO
0

Featured Post

Tech or Treat!

Submit an article about your scariest tech experience—and the solution—and you’ll be automatically entered to win one of 4 fantastic tech gadgets.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Configuring Remote Assistance for use with SCCM
Windows Server 2003 introduced persistent Volume Shadow Copies and made 2003 a must-do upgrade.  Since then, it's been a must-implement feature for all servers doing any kind of file sharing.
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…
Windows 10 is mostly good. However the one thing that annoys me is how many clicks you have to do to dial a VPN connection. You have to go to settings from the start menu, (2 clicks), Network and Internet (1 click), Click VPN (another click) then fi…

610 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question