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.
Related
I am using aptana studio v 3.4.2.201308081805 on windows 7, I know that v 3.5 is available because I was prompted to update to 3.5 on a different computer.
I have not received the update prompt on my macbook air or on my work computer. Does anyone know how to force aptana to update to v 3.5?
Aptana has removed version 3.5 due to several bugs.
Current stable version is 3.4.2
You can check here Aptana download
Check out the other Stack Overflow question from here. It's also about updating Aptana Studio. Basically, in your case, Aptana may not have the update sites list configured yet. You'll need to import the XML file containing these addresses (many people have had to deal with this, as show in the support thread on Aptana Studio's support site about adding update sites to Aptana. Also, check out this page on the Appcelerator wiki about common issues with updating.
I am trying to get an ASP.NET 3.5 site to run on a Windows 2000 machine (not my idea!!!) but am having some problems. I have been working through copying required DLL files from C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5 into my app bin directory. This succesfully got me past the "assembly not found" errors.
However, I am now getting the following error.
Compiler executable file csc.exe cannot be found"
How can I fix this? It is primarily LINQ functionality I am looking to utilise.
You are going to have many issues as .NET 3.5 is not supported on Windows 2000 (see System Requirements).
You can try to install .NET Framework 3.5 manually. It relies on .NET 2.0 runtime + some extra stuff.
See Microsoft .NET Framework 3.5 in
Windows
2000
for install steps.
See also More details on installing
.NET 3.5 in Windows
2000
for explanations.
Install a Virtual Machine with a newer Windows in it ;-)
Many 3.5 sites will work just fine in 2.0, you just need to compile them that way. I would have whoever built the app switch to 2.0 targets and see how it goes. If that doesn't take, the VM option is probably the best way to fly.
Save yourself some time and pain, install on a platform that supports 3.5.
Trying to circumvent minimum requirements usually comes back to bite you in the end.
Just because you can doesn't always mean you should. :)
Unfamiliar with the environment, but...
More of the framework (including csc.exe) resides in %WINDIR%\Microsoft.NET\Framework\v3.5 (e.g. C:\WINNT\Microsoft.NET\Framework\v3.5) - are these files on your installation and the directory in your path?
Are there any issues with running an asp.net 1.1 application under windows server 2008 64-bit web edition?
I have never tried it myself, but I did find the following pages that you might find interesting:
This blog has an in depth walk through of configuring ASP.NET 1.1 on Windows Server 2008. The author does not say if it is x86 or x64, so I would just assume its x86. But either way, it looks like the author had to jump through some hoops to get the ISAPI filter setup correctly.
I also found this thread on the IIS7 forums where someone discuses having poor performance from ASP.NET 1.1. on x64 Win2k8. So from poor performance I would assume it worked to some extent. Unfortunately towards the end of the thread the author mentions encounter 500 errors, and then the discuss stops :-(
So from what I've read I would guess that its possible, but I would also guess that you would have less hassle if you could find some alternative that didn't involve both II7 and x64.
I have recently been testing our application on 64 bit 2008. Our application is .net framework 3.5 but we had a few problems.
The main issue we had was with 3rd party components such as Aspose words which were not built for 64 bit and caused an error. Unfortunatly you wont know without trying it..
.NET 1.1 is 32 bit only hence the app pool would have to run as 32 bit and use the classic pipeline. I haven't tried myself and I would do all that I can to not have to install .NET 1.1 on a 2008 server but it should work.
No problem. Just follow intructions on
http://learn.iis.net/page.aspx/472/how-to-install-aspnet-11-with-iis7-on-vista-and-windows-2008/
The option "CGI Restrictions" (last step) is found on IIS7 admin by clicking on the machine name.
I'm pretty sure that the article at http://learn.iis.net/page.aspx/472/how-to-install-aspnet-11-with-iis7-on-vista-and-windows-2008/ is for NON-R2 versions of Windows Server.
As far as I know ASP.NET 1.1 cannot run (or at least, not run well) on Windows.
There are some band-aid solutions around that various people have posted / blogged but this isn't supported by Microsoft.
I'm a little confuse between the different SAPI version available.
First of all, I only find the SDK to develop with the 5.1 version, is there any SDK for the 5.3 version available, if not, why ?
Witch version can I use if I'm developing with the 3.5 version of the .Net framework.
Is there any good tutorial because the only one I found are pretty old (they use 2003 version of visual studio) : http://msdn.microsoft.com/en-us/library/ms986944.aspx
Is there any way I can use the speech API directly in Asp.Net web site in speech-to-text mode ?
Thx!
Wikipedia tells me that SAPI 5.3 was included in the Windows SDK, so go download that. SAPI 5.3 looks like it was included as part of Windows Vista, so I don't think you can use it in any other version of windows. The library is just a COM library, which means it's not dependent on your .NET version - i.e. you could use it in .NET version 1.0 even. In fact you could use it in almost any language because a lot of them support COM in some way these days.
I'll get your easy question out of the way, no you can't use the Speech API in any way from ASP.NET on the client's computer. If you're really serious about it though, you could look into either creating a Silverlight application which uses the Speech API on the client's computer, or alternatively look into constructing the voice data on the server and streaming it down to the user. However, both options would probably be quite difficult at the moment I think.
I learnt to use SAPI 5.1 from the tutorials on MSDN, just like the link you posted. They are old, I know, but they're all still relevant. SAPI 5.x hasn't changed for almost a decade now. Visual Studio 2008 can still do all the things Visual Studio 2003 could do (well, mostly I presume) and it definitely can use a COM library, so it's possible, you just got to use your brain a bit.
You should try the namespace System.Speech (it work's with VS2008 do not know if framework under 3.5 have it... and I am on Vista)
SpeechSynthesizer foo = new SpeechSynthesizer();
foo.Speak("Test");
You can have more detail here on MSDN
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.