This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
How to Deploy VB6 Applications?
The company I'm working for has this application that was written in VB6 last year. I've had the pleasure of working through just a few minor things here and there in it. However, now I've had a bit of a stumble. In the latest Visual Studios, whenever you build your application, any referenced .dll dependencies can be found in the bin/Debug(or Release) folder.
My question is that in the VB6 Enterprise IDE, where does the dependencies get placed when you make the .exe? I'd assume that they are in the same location as the .exe; however, when I copy that entire folder over to another computer, and regsver32 (in administrator mode, of course), and I try to run the program, I get told I'm missing a dependency. Thanks for any and all help.
It's been a while since I worked in VB but I seem to remember that you wouldn't copy the executable but would create an installation package that would manage all the DLL's, OCX's and such and register the necessary things with the registry for you.
Related
I've recently bought a new tower and used third-party software to port across all my development tools (another story in itself), including VB 6.0, all my third-party tools, and Btrieve. The only problem I have with Btrieve is more an annoyance than anything. On this new tower, I have to remember to run my compiled application once before attempting to run it from inside the IDE or else it will not load, and subsequently return a corresponding error when it attempts to open the first file.
If anyone else has encountered this and knows how to fix it, I'd much appreciate it.
After checking this page on Wikipedia I realized that I needed to focus on two files: w32mkde.exe and wbtrv32.dll
By manually running the exe file, it would load the engine and my application would then run in the IDE, but I still had to manually start the exe. The desired and original behavior on my older machine was that running my program in the IDE would automatically launch the sever exe. From the Wiki page, I learned that it was wbtrv32.dll that was actually called by the program, which in turn would call the exe if needed.
I had recentl ported over my old machine to a new tower, and many of the ocx and dll files in \windows\syswow64 did not make it. There seems to be no pattern to which ones, but I had to re-register those as I found them. There must be some link there, because when I copied-over the W*.exe and W*.dll files from my production backup folder to the syswow64 folder, it suddenly worked again. Likely just a corrupt copy of the dll file. I believe the reason that the compiled version ran correctly is because those dll and exe files were installed to the application folder, and were apparently okay, but not being invoked when run from the IDE.
Hope this might help someone else some day.
I am using Visual Studio Community 2017 (C++) with default configuration on Windows 10 (64 bit).
I have a single CPP file and I am trying to compile it.
The problem is that the "build" works fine, it says success, but the expected exe file is just not created.
I spent a few hours now trying all the available options - release/debug, 64bit/32bit, empty project/console app and many settings changes as was advised on various forums - no luck.
Does anybody know what could be the problem? I just can't find a solution for this.
I found my executable in my projects folder called "Release" (for x32) and "x64/Release".
Although I didn't see them either the first time going through the folders looking for it.
Alternatively I found this site with standalone build tools:
http://landinghub.visualstudio.com/visual-cpp-build-tools
ps: for the pros, I am still a big noob, so I can't tell if that site and tools is of going to be of any use, or even right, to the person asking the question.
So atleast I have added it and is for him/her to decide if so. ;p
regards,
E Karaagacli
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 years ago.
Improve this question
Can ReSharper 7.x be configured to work with Visual Studio 2013 preview?
The preview version doesn't appear to allow it by default - though I only tested by repairing ReSharper, rather than uninstalling/reinstalling.
I'm aware that ReSharper 8 is on its way and may be a better long term option.
Being able to evaluate a new IDE under the same conditions that I use VS2012 is imperative, so this would help massively in that goal.
UPDATE
It looks like the answer to this is that it cannot be used - the accepted answer demonstrates a possible, untested method of wiring it up but there are now 3 or 4 cases where the solution has not worked, including an attempt by myself to hook it up which unfortunately didn't work. As such, I've added this update to avoid misleading anybody who comes across this.
Warning: This has only been tried by me just now on VS2013 with the latest v8 EAP, this may cause crashes or slowdowns etc and I can't say how v7 would behave.
If you go into your program files folder, then open the VS2012 folder, navigate to Microsoft Visual Studio 11.0\Common7\IDE\Extensions .
From that folder grab the Jetbrains folder, and copy and paste it to the same location but substitute 11.0 for 12.0.
Then open the file inside the Jetbrains folder named extension.vsixmanifest in any text editor of choice (remember about running as admin) then inside find where at the top on approx lines 11 - 16 , you will have a section named VisualStudio.
Copy and paste this whole block and paste it again below (inside the SupportedProducts section still).
Edit the Version="11.0" to Version="12.0" and then save the file, re-launch VS2013 & you should now end up with resharper working.
Nice and simple :) Also for future reference this technique works on any extension, also some extensions are stored in AppData instead. Just thought I'd reply with this to make sure you got a helpful reply :D
I have inheritted several old VB6 applications that currently cannot be rewritten in .NET. These old applications all use ADO, and compile fine on my XP machine. Since switching to a Windows 7 machine, the applications compile fine, but when they are deployed (on XP machines), I get errors. This is a known issue that this Microsoft article discusses:
http://support.microsoft.com/kb/2517589
The article give a very detailed explanation of a workaround, which involved copying a ".TLB" file and registering it using "regtlibv12". When I attempt to register it, I get this error message:
RegisterTypeLib of C:\Program Files\Common Files\System\ado\msado60_Backcompat.tlb failed : 80029c4a
I have also tried registering this using the old "regtlib.exe" in the Windows folder, but got this error:
LoadTypeLib of C:\Program Files\Common Files\System\ado\msado60_Backcompat.tlb failed : 80029c4a
Because of this, I cannot continue with the work around. I would greatly appreciate any guidance anyone could give me on how to properly register this file.
Thank you in advance!
Put the .TLB file in an appropriate place like
C:\Program Files\Common Files\System\ado
Then open a new Project in the VB6 IDE (elevated, i.e. as admin). Choose Project|References... then click the Browse button. Navigate to the new .TLB file and open it. Check the box to select the item and close the References dialog.
It should be registered now.
If desperate, try VB Type Library Registration Utility.
You probably downloaded the file as C:\temp\Msado60_Backcompat_i386.tlb and didn't rename it. The example is for registering C:\temp\Msado60_Backcompat.tlb (note, no _i386).
Run the command with the correct filename.
Just to update this answer list based upon more recent information, Microsoft released KB 2640696 which addresses this issue in a more straightforward manner. This patch makes it much easier to deploy on your build machines and solves the downlevel OS issue as well.
A more complete picture of the patch can be found on the following blog post.
I am new in programming and I want to install Qt-Jambi in Eclipse in windows 7.
Can you explain it to me with a step-be-step procedure?
I have searched but I didn't find a easy explaining procedure or tutorial.
Thanks in advance
As a QtJambi maintainer, I provide this answer so as to help close off this issue for someone else searching.
There is no official way to install QtJambi system-wide, which might be the reason this answer has remained unanswered for so long. Since there is no answer to the question that was put.
There is an official way to install the Java JRE or JDK that is a well trodden path using the EXE Sun/Oracle release. But largely for Java application space and Java development space there are no official way of doing these things and the matter is largely left upto the application program and package things up and get the "ClassPath" correct for use with the application when that application is deployed.
So all I can advise to you are some ideas/tips on how you might do-it-yourself for development and application deployment.
...
Decide if you are developing for Windows 7 as 32bit or 64bit. If you want your application to work on all windows computers (WinXP/WinVista) then 32bit maybe your choice (as there are not many desktop application that need to use more than ~1.5Gb of memory, which is about the effective usdable memory you will get, if you need this or more then use 64bit).
Once you have decide which environment you are working you need to ensure you have that Java JDK installed. On a Windows 64bit system you can install both 32bit and 64bit JDk/JRE side-by-side. They end up in different directories C:\Program Files\Java and C:\Program Files (x86)\Java.
If you choose to go 32bit then maybe you will also use 32bit Eclipse (and see Trouble installing QT Jambi on a Windows 64 bit system for help with that). This may allow oyu to use the QtJambi GUI designer that was released (some years ago now) for Eclipse IDE.
Now you can select which QtJambi to download from sourceforge (or other download site). This maybe just a ZIP file which you unzip where you want on your system, then setup your development enviroment to point to the JARs provided inside it. It should not hurt to include all JARs in your classpath.
It can be useful to unzip the native JAR (that is the JAR that contains DLL/DSO inside it). Then use the unzipped directory as a -classpath entry to java.exe. The reason for this is that QtJambi will unpack these files since DLL/DSOs can only be loaded by the operating system when they are unpacked as regular files. QtJambi will attempt to unpack everytime you start the EXE which will slow down development.
Other than this take a look at the source of the examples and Launcher provided in the project GIT tree on gitorious (or maybe *-src.jar in the ZIP download).
...
To deploy QtJambi as an application (to give to a 3rd party to use your application) you simply need to ensure the -classpath is setup to include the QtJambi JARs you need.
It is also recommended to deploy the Native JAR unzipped for the same reasons as above during development. The JAR format of this data is more a convienience format to throw it around but an installed should unzip it.