I am working on a project developed in ADA on windows xp using GPS-GNAT 2006 and must port it to windows 7 however when trying to upgrade to a newer version of GPS-GNAT (2008+) the ada code throws exceptions, but on the 2006 version it runs but GPS-GNAT 2006 has issues with hitting breakpoints, opening the IDE, the open project button, etc. My question is are there known compatibility issues with Win7 and GPS-GNAT 2006? And what should be the best course of action to get this old code running on windows 7?
Thanks
You are mixing two things here: the GNAT compiler itself (for which you might be stuck with an older version indeed), and the GPS IDE, which you can upgrade independently of GNAT. As others have suggested, please upgrade to GPL 2015 for GPS, and keep the old compiler.
Related
Would Windows CE 5.0 binaries be compatible on Windows Embedded Compact 7 and 8?
I've searched the Internet for a long time with no answers that are thorough or definite enough concerning the backward compatibility of these OSs.
Also I've tried to find the ceappcompat app mentioned here; it looked like it was supposed to be in the Platform Builder tools found in the installation of Windows Embedded Compact 7 x86, but it wasn't there.
By way of experiment, I have found that Compact 7 is, in principle, backward compatible with respect to native applications. I was able to run x86 applications built against Windows CE 5.0 Standard SDK on a Compact 7 OS. However, Compact 2013 is a different story. As explained in the answer to a similar question on MSDN forum, existing Windows CE applications must be recompiled in order to run on Compact 2013. Reportedly, the breaking change in the new OS is the price paid for the ability to use the same Visual Studio 2012 tool chain for both desktop and Embedded Compact Windows targets.
I am about to upgrade my pc, and operating system at the same time. I was wondering what version of Windows 7 to get pre-installed, given that I want to do some ASP.NET development using Visual Studio.
Specifically :
Will all versions of Windows 7 run an IIS server & be suitable for ASP.NET development ?
Are all good for running SQL Server etc ?
Will Windows 7 have any probs running old versions of Visual Studio (Ie. 2003 & 2005 versions).
Are there any other things I need to consider ?
I'm probably going for the 32 bit version of Windows 7.
Thanks in advance,
Bazza
I would suggest you get the 64-bit version: there's really no reason to be running a 32-bit operating system in this day and age (unless you have some esoteric hardware that doesn't have 64-bit drivers, but that's exeedingly rare: especially on Windows 7).
I think IIS 7.5 is included in Home Premium, but I think the Professional SKU is probably the best bang-for-buck version. You don't actually need IIS for ASP.NET work anyway, the development server that's included with Visual Studio is usually the best option anyway (it doesn't require Administrator privileges to debug).
Other than that, they'll all run SQL Server fine, and I see no reason why older versions of Visual Studio won't run, either (there may be issues with UAC, but nothing too dramatic for day-to-day use).
Not exactly a programming question in the technical sense, but it's impacting my development nonetheless and I'm hoping someone here might have encountered and solved this issue before.
I recently got adventurous and installed Office 2010 beta onto my PC here, and I've noticed that Visual Studio has begun to hang whenever I'm editing an ASPX file, sometimes right away, sometimes after a few minutes. In my research I came across this post:
http://abdullin.com/journal/2009/5/12/visual-studio-2008-locks-or-freezes-in-aspx.html
It seems to imply that there's a dependency between Office and Visual Studio. Is anyone here successfully running Office 2010 64-bit with Visual Studio 2008? I'm on Windows 7 64-bit, also.
Josh
Edit: I have confirmed that the Setup.exe file referenced in that post is in fact being run by VS. It is indeed a vestige of the Office 2007 suite. I moved the directory it was in, and (of course) the process isn't spawned, but VS hangs on "loading cache" on this project. I think I'm getting closer though.
Hope this helps:
http://blog.hinshelwood.com/archive/2009/07/19/office-2010-gotcha-2-visual-studio-2008-locks.aspx
Unfortunately, doing a repair install of the Office-based Visual Web Developer component wouldn't work — the setup application kept crashing. I ended up solving this problem by doing a complete reinstall of Visual Studio. For some reason, doing a simple repair wasn't possible — the VS setup kept crashing, too.
I did a manual remove using an uninstall tool designed for the VS2008 RC. It did a complete install of all VS components, after which point I reinstalled VS2008, which in turn reinstalled the Office-based visual web developer component.
It was a long and painful process, but it worked. It didn't seem to be a direct incompatibility between Office 2010 and VS2008, as we have another PC here with the same combination that wasn't having the problems. I believe it had to do with the fact that my PC originally had Office 2007, which I had to uninstall before installing Office 2010. The other PC that wasn't having this problem never had Office 2007. I can only assume that the uninstall process for Office 2007 either removed those Visual Web Developer components or removed dependencies that were originally put in there by the VS2008 setup program.
office 2010 runs on wpf and its major portion is build on dotnet framework. And there is always connectivity between office and vs coz vs can make office apps also. If you use office 2010 as your default for aspx page editor and vs is also opened with the same project. it will sometimes hang due to lack of resources and also vs 2008 was made for 32bit os, so if ur running it on 64bit os with office 2010 64bit it can sometimes cause problem of resouce management. Already wpf uses hell lot of resouces and then 32bit vs 2008' connection to it will use more resouces.
So what i suggest is try to use 32bit 7, 32bit office 2010 ans vs 2008.
Regards,
Apurva
I have the unfortunate task of fixing a legacy ASP site that was migrated to Windows Server 2003, and I know nothing about ASP. The main issue appears to be with ASPSmartUpload, of which I have version 2.3 installed. According to http://foradvice.net/smart_upload_faq.htm:
FAQ: does aspSmartUpload work on
Windows 2003 server ?
Yes, last versions of aspSmartUpload
work fine on the Windows 2003 server.
If you upgrade your OS and used an old
version of aspSmartUpload, you have to
download and setup aspSmartUpload
3.2+.
Of course, aspsmart.com doesn't respond and any Google result for "aspsmartupload 3.2" points to the dead link. The latest version I can find anywhere is v3.0, on some dodgy-looking DLL download site.
What is the best way to resolve this, or can anyone provide a working link to version 3.2 of ASPSmartUpload? Thanks!
We searched for quite a while before finding these dlls.
Here is the link for the ASPSMARTUPLOAD.DLL Usage page that tells you how to install it and a link for downloading version 3.3.
From what I understand, windows server 2008 requires version 3.2 or higher, but we couldn't find version 3.2. I believe version 3.3 will work the same.
One other item, we had to get msvbvm50.dll VB Runtimes for this to work on windows server 2008.
Once these files were registered the server restarted we got past this issue.
Fortunately I have a copy of the original v3.3 distribution.
I've shared it here.
So, much to my annoyance I discover (after lots of research), that when running 1.1 and 2.0 dot.net frameworks on a 64bit 2003 install, it removes the asp.net tab from the IIS properties. I've tried the registry hacks, I've tried registering 32bit versions of both frameworks, and no luck. My only work around is running the excellent ASP.NET switcher from Dennis Bauer.
Does anyone else have any insight?
Also, you might try running the 32-bit version of MMC. IIRC, MMC can only load extensions that are the same bit-ness as itself, and the .Net 2.0 extension is 32-bit only.
That said, the tool you linked in your question is very useful for working around this issue as well.