Sorry for the noob question,folks. My new version of Vectorworks CAD 2022 won't run on my Win 7 x64 due to a missing procedure entry point. My laptop is too old to upgrade to Win 10 and I was hoping for a workaround, besides buying a new laptop. I tried downloading and installing a new kernel32.dll (probably for Win 10) that included the needed function but Windows 7 would not start up afterwards. Are my only options to (1) stay with the older version of Vectorworks or (2) buy a new computer? Thanks.
I've some .vbp,.frm files and i want to open them with VB 6.0 but i am using Windows 8.1 is there any version of Visual Basic that is compatible with Windows 8.1.Please do suggest me.Thanks in Advance.
Whats not working? Microsoft is supporting run time files for at least a few more years works up to 10 and maybe will be for a few more versions, install vb 6 and it should have no problem running unless the systems messed up.
As indicated by others, the VB6 development tools can be installed and work (with limitations) on all versions of Windows Longhorn (including Windows Vista, Windows 7, Windows 8, Windows 8.1, on up through Windows 10). Most of the limitations are project types rendered useless when Microsoft ripped away the infrastructure for them as they mutated IE and IIS over the years with little regard.
So without a license for VB6 or preferably VS6 there isn't much you can do with these files. If the projects are fairly simple you might get somewhere trying to make the completely unsupported VB5 work if you have a license for that, or if the project files are for even simpler applications VB5CCE might be of some limited use if you have that.
But in general there are no other products that can use these files to any useful extent. So as already covered many times in other questions here and elsewhere you need VB6/VS6 and the only remaining source is an MSDN Subscription or used or remaindered copies that may be for sale here and there.
I just formatted my computer not even a week ago after being on Win 7 for a long time. I thought it was safe as at work I been using Windows for like a year now and have not had to go to load Windows 7 up since switching.
Now I just got a project that is apparently set to .net 4.0.3 version and won't be upgraded at this time.
I tried downloading .net 4.0.3 on Windows 8 but it always fails for me. I get
"KB2600211 does not apply, or is blocked by another condition on your computer."
I thought maybe if I install VS 2010(as they want me to use VS 2010 becuase they are a bit worried VS 2012 will do something funky to the project and mess everyone else on the team who are on Windows 7 and Vs 2010).
Anyone know how I can get at least 4.0.3 on windows 8? I don't want to format, took so long to get up to speed and won't be able to do Win Phone 8 programming anymore.
I would also have to stick it on my other HDD as my SDD can't fit both OS on with VS on it. So I will have a very slow OS and very fast OS.
The problem is that .net 4.5 is an in-place install which replaces .net 4.0. You cannot have both installed at the same time and Windows 8 comes pre-installed with .net 4.5. For the most part you should be able to just use .net 4.5 as if it were .net 4.0 but there are some breaking changes. You might be able to uninstall 4.5 and then install 4.0, but that sounds rather risky.
At a previous job, we didn't upgrade to .net 4.5 for exactly this reason. Until everyone is upgrading at the same time, there can be substantial compatibility issues.
For a list of incompatibility issues see here. Note that this doesn't cover any places where your app may have been depending on a bug in .net 4.0 which is now fixed in 4.5 or any things like this where a type is moved to a different assembly (these are not considered breaking changes, so they aren't listed in the incompatibility list).
I know traditionally its best to install programs in the order they were 'born' as that's generally going to avoid more problems.
Are there any known chronological dependencies between these two programs?
It works on my machine.
I just did it a day or so ago and had no problems. I was surprised at how smoothly it went, so if that's any indication of the usual, it should be a breeze.
Visual Studio is pretty good about installing to a particular directory, with the exception of support components (which are detected as already-installed and skipped). When installing 10 after 11, only 10 itself and a runtime or two were needed. Both 10 and 11 have been working perfectly since, including 11's support for compiling projects as 10 (to support XP, which was why I installed both).
It does get a little bit messier with installing 9 (2008), but you can typically install that after 10 and use the back-compiling. I have no idea what happens if you install 11, then 10, then 9 (it could work).
VS 2012 broke 2010 for me, but I don't know if it would break the other way. Certainly, don't do it on your production environment.
Workaround : freely downloadable Windows SDK has the vc10 compilers and toolchain, and you can use it when compiling from VS2012. Just select appriopriate platform toolset in project options.
I want to trial Windows 7 but wondered if anyone who has done so already ran into any issues specifically related to development?
i.e. problems with VS2008, SQL Management Studio and SQL Server, MySQL, PHP etc. etc.
Examples from XP -> Vista: in Vista there was a sudden loss of an SMTP server. And there were initially (if I remember correctly) issues with VS2005 with I seem to remember a patch coming out later to remedy.
EDIT: or on the contrary any big advantages or benefits to developing on Windows 7!
I been using windows 7 for a while now.
I been using VS2008, netbeans, tomcat, sql manager studio, mysql etc...
And i actually find it more stable and faster then windows vista.
There aren't many advantages to developing on Windows 7 before it's released. Most development features are a function of the IDE, not the OS. So, you might want to consider instead if you should be developing on Visual Studio 2010 instead of VS2008. Instead, you're more likely to have compatibility issues, although for the most part, Windows 7 is much more compatible with existing software than Vista was when it was in beta.
There could be one advantage to developing for Windows 7 before it's released -- you have a head start in taking advantage of features that competitors haven't yet, giving you an advantage in the market. That's the theory at least. That assumes you're going to develop something that uses a feature only available in Windows 7. That assumes you wouldn't be better off with the larger number of sales you'd get by developing something that works on existing platforms.
The only issue I've encountered so far involves compiling older vanilla C programs with Visual C++. You're usually presented with an error like so:
mt.exe : general error c101008d:
Failed to write the updated manifest
to the resource of file
".\Release\SomeProgram.exe". The
binary is not a valid Windows image.
You have to add an empty resource file to the solution.
More on the issue here.
I've never gotten any of the new audio stack examples working; thus this question. API works, documentation is... a bit lacking at the moment; sure to be fixed by RTM.
Other than that, Windows 7 has been faster than and just as stable as Vista (2 crashes from RTM, 0 crashes after SP1) was for me. Truly, you should be developing on Vista and testing on Windows 7 RC as a general practice with respect to pre-release operating systems; but I think we'll get away with it just fine in this particular case.
My advice would be to not develop on Windows 7. Note that I don't mean you shouldn't target it as a platform, just that you should be doing your development on a stable platform.
I personally won't trust a new release of Windows (or Linux for that matter) until it's been in the wild as a proper product (not release candidate) for many months. For Windows, I tend to wait until the first real service pack plus a month for all the nigglies to be fixed.
For Linux, I'm still using Ubuntu 8.04 LTS, not 8.1, and certainly not the 9 alphas.
Test machines are another matter, you should always have one at the "latest and greatest" level for testing, but I consider the development machine of prime importance, needing a stable platform.
No problems from my end yet, been working on a c# app with visual studio 2008 x64, and php web apps with dreamweaver cs3 and netbeans.
Windows7 seems to be just vista with more bells and wistles and a bit more responsive, not to sure if to much really change "under the hood" so to speak. But I have nothing to back that statement up with...
I've been using Win7 for a couple of months now and never had a problem. I went straight from XP to 7 and the only problems I faced were related to configuring SourceGear Vault to work with IIS7...other than that,it's been all good.
I use VS 2005, VS 2008, SQL Server 2005, Infragistics NetAdvantage, and a couple of third party components.
Although I haven't seen any advantages for the development side of the applications, I'd recommend you to upgrade to Win7 only for the better feel of a complete OS. I mean XP was good, but I really dig Win7.