I am using visual studio 2010 on Windows 7 64bit.
I compiled and ran a simple application basically a thing a child could make.
Well the second it started to run, it froze my computer and rendered it unresponsive.
It continues to do this every time and for every application.
Any ideas why this is happening?
I figured out what was wrong.
COMODO Antivirus/Firewall blocks all applications from calling DLL's, you have to click "Allow" on the dialog that normally pops-up. But since its a DirectX DLL for WPF (since WPF uses DirectX) it froze windows along with my app.
Related
My task is to make a simple application that connects to the internet (using Wininet) and downloads a text file. It then displays the data in a listBox widget. The requirement was to make a GUI based application, so I used Windows Forms in Visual Studio Express 2010.
The application runs fine on my PC, however I realized that it runs only on my PC. I installed .Net 4 and Visual Studio 2010 redistributables on another PC and it worked fine there. Now, the person for whom I'm making this wants maximum compatibility on windows PCs. I'm totally stuck here.. should I switch to an older version of VSE?
From what I could search, using /MT instead of /MD would cause the application to link statically, however my app also uses /CLR and these are incompatible.
Any ideas?
Note: I've previously made a similar app (downloading and displaying) with console output and it works perfectly fine everywhere.
Dependens on what is meant by "maximum compatibility on windows PCs". If you can bundle the required redistributables, your program should run (as you found on the second PC), as long as the windows on the PC is capable of executing the binaries (e.g. not a 32 bit PC trying to execute 64 bit binaries)
I have been in your situation.
I can give you my free .NET-application-runner (RunNetApp.exe) that automatically installs .NET Framework 4 before running your application for the first time. If the framework is already installed on target machine, it only runs your application.
I also suggest changing application's framework to ".NET Framework 4 Client Profile". It's setup is about 40MB (in comparison to 200MB of full ".NET framework 4").
Is it helpful?
Bit of a strange and very annoying problem.
I'm using Visual Studio 2010 for an ASP.NET webforms project. I was able to set breakpoints in an activex control, load the page and then attach the Visual Studio debugger to the Internet Explorer process running (shows up as Type 'Script, T-SQL, Managed) then reload the page and my breakpoints would be hit.
However, after several small subtle changes (and lots of tidy-up changes), when I do the same thing, my breakpoints are not hit. The breakpoints look okay - the main change is when I look at the Debug > Windows > Modules screen, there are now no references to the iexplore process, even though the debugger is still connected to it.
I'm a bit reluctant to undo all my changes but I suspect that it might be down to ip addresses. Most of the code should run as an ipv4 address but I suspect that the Visual Studio debugger is running with ipv6 address.
Has anyone come across this type of issue, where ip address versions are messing up debugging processes?
Okay, found the solution to this after a week! It was nothing to do with IP addreses. The ActiveX component was limited to .NET 3.5.0 and so when it was loaded by IE, it ran in .NET 2.0. The rest of the project was .NET 4.0 and when Visual Studio was debugging it automatically debugged code type 'Automatic: Native' which defaulted to .NET 4.0. Although I could attach to the IE process and all the breakpoints looked ok (solid circles), none of them were hit because no symbols were loaded. Clicking the 'Select' button when attaching to the IE process, allowed me to choose Managed(v2.0, v1.1, v1.0) code and the breakpoints were hit. You can't debug both .NET 4.0 and .NET 2.0, but you can use two seperate instances of Visual Studio to debug your complete project.
Hope this helps anyone else who trips over this one like I did.
I have a Silverlight application that I can run from Internet Explorer 8.
When I attempt to host it in a Winforms browser control as described here: Silverlight Hosted in Winforms it display a web page that says "To view this content, please install" and has a "Click now to install" button.
Unfortunately, SL4 is already installed. However I did try to follow the instructions. But was prompted, of course, that SL4 was already installed on my system.
I seems that at one spot IE/Silverlight cannot see that Silverlight runtime is installed, but at anoter spot it can see it. This has become a significant roadblock.
The client OS is Win 7 64-bit. I have no idea if other versions of OS are exhibiting the same problem.
Silverlight (the plugin) is 32-bit only. You can not run it from a 64-bit application.
If you can [easily] force the application to run in a 32-bit context, then you're in luck -- change the "target" of the VS project from "Machine Independent" to "x86".
The above situation describes exactly what I ran into when trying to run SL (32-bit) in a Windows Sidebar Gadget (default 64-bit on Windows 7 64-bit); this is somewhat interesting, it implies that all (or at least almost all of) the components behind IE are 64-bit ready. The "holdup" and why IE normally only runs in 32-bit is that it's a chick-and-egg problem with all the plugins, BHOs, and ActiveX components used. However, the (IE) Browser Host will happily run as 64-bit.
I'm using Windows 7 Professional (x64) and having installed .NET 4.0 RTM on my machine.
Since 2 days I'm noticing that every WPF application that I'm trying to run hangs and becomes non responsive (a not responding text is appended to it's title bar) and it's painted white.
There is no info regarding any exception, no error message. Nothing. Even the Event Log shows that there was "application hang" event (code 1002) and nothing more.
This problem is for everything that is written in WPF, even for products like NHibernate Profiler and other stuff that I was using on a regular basis without any issues.
Tried to reinstall .NET 4.0 and nothing changed. Any ideas why this might be happening?
I had the same problem. It was a corrupt font cache!!
See http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/7cc032c1-5f4d-4518-adc6-f53afd051e6b for a solution.
If I had to guess I would say video drivers. It might help to try attaching Visual Studio's debugger to the hung process (Debug -> Attach to Process) making sure that Managed Code is the selected debugger type. Then you can break into the debugger and maybe see a common stack trace.
We have a large winforms program. On one computer if you are running the program and open IE8 the winforms program freezes and doesn't come back. But if you already have IE8 running when you start the winforms program everything appears to be fine.
The same thing happens regardless of how you start IE8 (normal, no addins, or 64 bit).
My dev box has the same os, motherboard, processor, and memory and it runs fine.
This is on Vista Enterprise x64 Q9550 with 8GB ram.
It runs fine with Firefox 3. The weird thing is there are no web browser controls in the app or anything that should make it related to IE.
I would first start by trying to open a different browner (i.e. Chrome) to see what happens there. My guess is that will work but at least its another point of reference for solving the problem.
Wasn't really browser related. Some of the controls were created on a worker thread so they had no access to the Windows message pump.