Moved from IIS6 to IIS7 (Windows 2008 Server 64 bit).
I'm looking for an upload component to use with my Classic ASP.
Is there some .Net code that does this?
You can do this in Classic ASP in code only without using a component. There are several version sof this code but Free ASP Upload seems a popular choice.
Related
I wanted to host my .net core API in Go Daddy Linux Server and also .net Core Web APP is there any possibility to do that. Also I have seen lots of tutorials to make that happen in Linux server which is for cloud but doesnt work the same scenario for any another on premises server.
If anyone have this experience or can only suggest that if there is possibility for hosting in the go daddy linux server it will be really helpful
It seems that you need to ask them whether they have support .net core on their Linux hosting package. I ever worked with them in the past 8 years ago, I didn't like their support, but I don't know now, maybe they improve better. If you want to use .net core on Linux, Digital Ocean can be good option. I also .net user here but I always use Windows to deploy my .net. From Classic ASP until newest .net core project, I always use Windows Server.
i'm getting started with asp.net vNext and i've found something that i cant understand if is a limitation on the DNX or if is something still not fixed.
When i'm publishing a simple webapi, as simply as the the default VS2015C template, my IIS 7 says:
IIS 7.5 or higher is required.
Is there some workarround or is really a limitation?
According to the latest community standup, the HELIOS integration between IIS and asp.net 5 was stopped. Ongoing the only server provided by MS is kestrel. You have to start and integrate kestrel into IIS by reverse proxying it.
This is quite normal in the Unix world and the .net team had to reduce the maintenance effort here.
Answering your question: Considering the Announcement I think practical usage in an Windows Environment via HttpPlatformHandler is only possible IIS8+.
ASP.NET 5 never has and never will support IIS 7 (Windows Vista and Windows 2008 both have IIS 7 only); IIS 7.5 and higher is actually required to bootstrap the dnx. If you want to work with ASP.NET 5 you must be running a Windows 7 or higher client OS or a Windows 2008 R2 or higher server OS.
There is a new requirment where from classic asp page i have to interact with linux server and fire a page in that server. never worked for cross-platform, how can i do it?
We are developing ASP pages for a Windows CE device. We need to debug the ASP pages for reducing the development effort. The ASP pages uses a COM component for getting data from the device. The web server running on the Windows CE device is Httpd.
How can we debug the ASP pages running in Windows CE device?
You've run into one of the many joys of developing using the ASP server that ships with Windows CE. There is usually no way to do live debugging so you're largely relegated to using alert statements or DEBUGMSG from a COM component.
The one exception, and it's not all that easy either, is if you've created your own OS image and you have a BSP with KITL enabled. In that case you can build an OS with the debug version of the web server in it, deploy the OS from Platform Builder, attach with KITL and set break points down in the server code. You can then use those to step into the parsing of your own ASP page. It's a complete headache.
Shameless plug
Attempting to write anything useful with the built-in ASP server is so bad that we actually wrote a complete replacement. Our Padarn Web Server supports a subset of ASP.NET, was designed for CE (though it runs on the desktop as well) and best of all you can use C#/VB.NET and the Visual Studio debugger for your page code behind. The only downside is that it's not free - though if time is of any value, it certainly costs less than trying to use the built-in server.
well, according to what I've found googling around, it's imposible... (maybe with with windows xp 64...)
but I thought that maybe someone could find a way to achieve it, or at least some workaround...
http://www.iisanswers.com/IISFAQ.htm
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.inetserver.iis&tid=14654991-875f-4cc6-a853-7e9f3bb96bc3&cat=en&lang=en&cr=&sloc=en-us&m=1&p=1
--
ps: I need to debug classic asp code, and my production environment is windows 2003, while my development machine is windows xp...
--
edit:
just to clarify, I can already debug classic asp code in iis 5 with vs 2003 and 2008, it's just that I stumbled upon a (very silly) bug that only appeared on iis 6 (when IIS 5 received and empty http status, it just assumed 200, while iis 6 kept asking for my credentials in an infinite loop, it was very silly in deed, but took me a lot of time -and cursing- to discover it)
IIS 6 cannot be installed on Win XP. However, debugging classic ASP code is possible on Windows XP / IIS 5.1 using Visual Studio 2003 and up. You will need to configure IIS 5.1 to "enable ASP server-side debugging" (disabled by default):
IIS settings http://www.freeimagehosting.net/uploads/f1a6f781b9.png
Here is a more detailed article on how to debug classic ASP pages in Visual Studio - link
(NOTE: When running on XP Pro/IIS 5, you need to attach to dllhost.exe instead of w3wp.exe)
You posting in your 2nd link is correct. And read the faq. That spells out why it can't be done.
One option you can do is have a virtual machine of Server 2003 running on your laptop.