I have an executable file which is .net 4.0 framework compatible.
When i am running it into windows 7 it is running normally, but when i tried to run it on windows vista then it is not running.
Please tell me is it possible to run 4.0 framework application on vista?
If yes then how, if not then why?
Most likely the executable fails to run because its dependency on .net 4 is not being met. Vista comes with .net 3 installed, but no later version. Which makes sense because Vista pre-dates .net 4 by many years.
Install the .net 4 runtime on the machine to resolve the problem.
well it was because of some dll files difference between windows 7 and windows vista.
i got them and solved.
Related
I am running and supporting a PowerBuilder 11.2 application running in windows 7 64bit environment. The previous version of this program ran without a problem, and 99% of this new program runs without a problem. However, when I run a specific bit of functionality, at times the program throws an exception "Sybase PowerBuilder 11.0 has stopped working" Problem event name APPCRASH Application Name PB110.EXE, Fault Module Name PBSHR110.dll, Exception code c0000005 in the dev environment. In the compiled version running on the client machine the error "A breakpoint in an application indicates a program error. After this dialog is dismissed, the application will continue to run, but it may be in an unstable state" and the program closes
There are shared PBL files throughout this whole application. It is a framework that supports 6 MDI programs. I have performed a full build on the main objects and it compiles without error. The other programs that in the framework that use these common objects to not have this problem. I have tried to step through the code doing a debug, but when I step through the code, it does not crash.
I have re-installed PB 11.0 and the PB 11.2 upgrade again and of course rebooted numerous times. I am at a loss here. I have tried everything that worked before and have spent over a week trying to find something online, so I am now appealing to the group. Any help at all will be so very much appreciated. Until then, I'll keep trying.
Thanks.
John
It could be that PB 11.2 is not listed as being supported on Windows 7. A lot of times you can get lucky, and most applications will still work on unsupported OS's. Yet, an update may be released that breaks something. You may want to try downloading the latest release of PB which is 12.6 and migrate a copy of your application to that version. You will at least be able to rule out if that is the issue or not.
Enclosed is Sybase PowerBuilder Enterprise version 11.2, which is
compatible with the following platform and operating system
configurations:
Microsoft Windows XP with Service Pack 2
Microsoft Windows XP Tablet PC Edition with Service Pack 2
Microsoft Windows Server 2003 with Service Pack 1
Microsoft Windows Vista Business Edition
PowerBuilder 11.2 builds 32-bit applications, but supports deployed
applications in both 32-bit and 64-bit environments on the Vista
operating system. For more information about using PowerBuilder on the
Vista operating system, see “Vista Support” in the online Help. For a
list of issues that have been found on the Vista operating system, see
“Vista issues”.
Microsoft Windows 2000 with Service Pack 4 is supported for deployment
only. All support for this platform will be discontinued in future
releases of PowerBuilder.
The subject says it all...
I am not, however, asking if the VB5 IDE will install and run on Vista/Windows 7 - just the project output.
Thanks
[UPDATE]
I found some more information that seems to show that not only will VB5 apps run under Windows 7 (x64) - but the IDE does too.
http://www.vbforums.com/archive/index.php/t-619859.html
[UPDATE]
Thanks Jay, It makes sense that these programs wont run on x64 (any O/S) - I don't know how the vbforums member got it running on Win7 x64.
Yes, it does. I have several applications(.exe files) compiled with VB5, which I can run on my 64 Bit W7 machine without any extra setting.
I have been trying to install and run a program written in vb 6.0 on windows 7. It was working fine installing and running in windows xp. The error message after installing and running it say that
Run-time error 339" : Component voice.ocx or one of its dependencies not correctly registered: a file is missing or invalid.
This program has voice recording things.
I manually register that ocx component but still error that shown like
The module "voice.ocx" failed to load.
And I try to install VB run-time and still shows the same error. I believe that Windows 7 support vb 6.0 programs.
One thing here I am not sure of is that the ocx component I have is whether 16 or 32 bit version. I don't think we cannot register 16 bit version ocx in windows 7.
And I also try to install and run in compatibility mode or even as administrator. I think it is a platform related issue? And it might be some other work-around. So, I appreciate your hints or clues on this program runnable in windows 7.
Thanks in advance.
Regards,
SEE
Just encase anyone else sees this.. here is what I did
I knew the program was running on Windows XP, with visual basic installed. I had only been given the exe and the MDB. So I created a virtual machine (stick with me) of Windows XP, installed visual basic and test the app. It was fine. Then I downloaded a dependency tool called Dependency Walker from http://www.dependencywalker.com/. I installed this in the virtual machine and asked it to open my exe.
Once this was loaded I ignored the warnings and asked it to start profiling. I ran the app, stepped through everything I could see, then exited the application. This left me with a log of the DLLs that had been accessed. Slowly I went through these checking if they existed on my windows 7 setup, when one was missing I copied it to my application directory and then from an elevated command prompt run "regsrv32 [missing_name.dll]" until there were no files which my windows 7 desktop didn't have.
the application then worked fine! This may not work all the time, because of the way third party OCX's or DLLs have been written. But it may help someone out.
Few of old Win32 components are not supported in Windows 7. There are possibilities of failure of a VB Program in Windows 7.
But there are some possible ways to fix those.
Check the following links to avail the same.
http://www.personalcomputerfixes.com/general-errors/how-to-successfully-fix-the-339-runtime-error/
http://social.msdn.microsoft.com/Forums/en-US/vbpowerpacks/thread/8cb5ab97-8407-4e49-8db6-30dcef87cbd1/
http://yang.articlesbase.com/operating-systems-articles/simple-solutions-on-how-to-fix-runtime-error-339-1830111.html
I have developed several programs with VB5 on a WinXP32 machines and then installed them on Windows 7 (32 and 64) PCs without problems.
This applications use different OCXs (16 and 32 bit version) and till now I never get problem with them. Thus I do not think that the VB5 or Vb6 could have any issue on Windows 7 machines.
On the other hand I would point out the module "voice.ocx" and investigate if it can run on a windows 7 pc, because as Katturaja sais some old ocx have problem on win7. To do that, I would create a simply VB6 project that uses voice.ocx (just an Hallo-World"), then create the installation pack and finally try to install on a clean win7 machine (for example a virtual machine). In this way you could isolate the problem.
I hope this could help you.
Question from a Linux/Mac developer: I have compiled a 32-bit .dll (release flavor) under Windows 7 using Visual Studio 2010. Should this .dll be usable under all flavors of Windows 6 (a.k.a. Vista, if I'm not mistaken)?
Many thanks and RTFMs appreciated,
John Clements
In general: yes.
All current versions of the .Net framework run on both Vista and Win7.
Note that if you make calls into the native platform, either directly or via the Windows API Code Pack, you could have portability problems if you use functions available only in Win7. But for just straight .Net development, you should have no issue in running on any supported version of Windows.
Yes, the dll format didn't change for Windows 7. Only thing to remember is that if it's a .Net dll, the target system must have the proper .Net installed or the appropriate C/C++ runtime.
You're supposed to #define the _WIN32_WINNT macro to tell what version of Windows you want to support. The default in the SDK that ships with VS2010 is 0x600 which avoids you ever linking to an API function that is not available in Vista. So, yes, you're probably good to go.
Firefox depends on an extension and plugin installed by the .NET 3.5 installer to run XBAPs. Unfortunately, in Windows 7 the .NET 3.5 runtime is already installed.
Does anyone know how to get a hold of these plugins/extensions so you can actually deploy XBAPs to FireFox on Windows 7?
Turn out, the answer is to copy the DLL of the extension out of another (presumably XP) machine that can run the .NET 3.5 runtime and deploy it.
I'm uncertain of the legality of this maneuver, but it works.