We have a solution with a .net core and we use a classic asp front site.
Our .net libraries use nlog, and I have to implement this feature on the front as well.
I searched the web and found one example from an old nlog version (back in 2007) usable as an activex. I try with nlog v4, but it doesn't seem to work.
I saw on the nlog site that "the classic ASP (so non-ASP.Net) are still in the NLog package (4.0)". What does it mean ? I didn't find any code sample or documentation on this feature.
Can you provide a simple example on how to use nlog in a classic asp page ?
According to this change log and this post, starting from version 3.0 COM Interop which provides you to use the library in Classic ASP support removed from NLog.
You can use v2.1.0 the latest COM Interop supported NLog release by registering the assembly on your web server.
This seems to be the easiest way to accomplish NLog in Classic ASP but with the lacks of number of new features that you may require of course.
Related
Which version of Visual Studio can be used to open a project which is built as ASP Web project
I have Community edition 2019 Does this support ASP projects?
I know these days no one is using ASP for building web apps The purpose is to maintain an existing ASP solution for a couple of more months 9If any bug fix requests from the client comes ) and start to build a new project using the latest version of Microsoft technologies
Visual Studio
Most versions of Visual Studio support editing Classic ASP code, couple of things to keep in mind though.
Frontpage Server Extensions is no longer supported, the best approach is to use a mapped drive or better yet store the code in source control (Git, SVN etc.) and work with the code locally (can bind to a local instance of IIS).
The IDE can be quite cumbersome for working with Classic ASP as it's designed for more modern technologies.
It also has sophisticated debugging through the IDE via the "Attach to process" which will work with Classic ASP running in IIS as long as the web application has been configured correctly for debugging. See How do you debug classic ASP?.
Visual Studio Code
Another option is Visual Studio Code which is a free IDE built on the principle of open source projects for cross-platform. It's becoming a popular free IDE for many developers rivalling the likes of Atom, Sublime etc.
It's lightweight and extensible through extensions, there are already some useful extensions for Classic ASP including this one;
Name: Classic ASP Syntaxes and Snippets
Description: Classic ASP Language Support and Snippets from tmBundle
Publisher: Jintae Joo
It also has built-in support for popular source control solutions like Git and more powerful available through the extension marketplace that is built into the IDE. If you do use Git would recommend installing the GitLens extension.
Every version of visual studio since I started with 2010 (was there something before it?) handles Classic ASP just fine. I'm on VS2019 right now.
I even have a project which is a combo Classic ASP, Webform, and MVC all in one project, with some session sharing, and I routinely code and debug in all. The only limitation is that when you debug, you have to choose whether you're debugging Managed code or "script".
With each I "attach to process" and choose which code I want to debug. Classic ASP debugging is fantastic, and I can't believe more people don't do it. I see basic questions on here which would easily be fixed with standard debugging techniques (settings breakpoints, evaluating variables).
The ONLY thing which isn't supported is code formatting inside <% %> blocks. If I ever get some time maybe I'll make an addon for it.
I'm looking for an Angular template for Visual Studio 2017 but I do NOT want to use the Core libraries as that requires me to rebuild all my re-usable libraries etc., and I will NEVER host my website on a non Microsoft platform (likely to put it into Azure only).
It would be nice if sign up / sign in is included.
I've tried to "convert" a core project to classic ASP .Net website with a "hack" mentioned on SO but encountered MANY issues
Any suggestions would be appreciated
Maybe you find a suitable template in the sidewaffle extension (http://sidewaffle.com/)
I recently discovered that Microsoft makes the .net frameworks source code open for the public and asp net stuff too.
Just wondering is it possible to compile/customize this and use it as a replacement for the official version?
What about compiling the .net for lets say mono/linux?
What about using the asp net source to compile it with mono?
Yes ASP.NET webstack is open sourced and it can be customized as you want. Note, ASP.NET WebForms is not opensourced only WebAPI, MVC, SignalR and WebPages is open sourced. Also IIS is closed source the last I checked it.
.NET library is but just a bunch of codes and as with any code, it can be customized as necessary.
As with Mono, I am not very fond of the distant cousin of the original .NET. It feels clunky at best at the moment and keeps changing everyday. Its best to stick with Windows for .NET for now.
Is it possible to achieve a goal specified in the question topic in ASP .NET for instance with existing controls like ScriptManager or any other controls? I'm using ASP .NET Web Forms 3.5.
Yes. You can use the bundler tool. IF you aren't on the latest version of .NET, you can use the nuget package bundler.net to achieve the same.
http://www.asp.net/mvc/tutorials/mvc-4/bundling-and-minification Here's a reference guide to using the bundler.
one thing is not clear to me that in asp.net 1.1 there was asp.net project type but from 2.0 version there is no asp.net project type option rather there is option called website type project.in website type project no link is created with IIS.why Microsoft design in this way from 2.0 version. i think there must be solid reason & advantage behind it and also tell me why no dll is created in bin folder until publish the website in version 2.0.
please explain the reason,advantage and MS Thought behind it if anyone knows the reason very well.
With ASP.NET 2.0, Microsoft split the concept into two different project types: the Website project type you're describing, and the Web Application project type. The main difference is the Website project type is designed to be folder-based, lightweight, JIT - essentially low-overhead where no overhead is justified. The Web Application project is a "traditional" project type: assembly-based, with a project-schema and optimized for precompilation.
In my experience the Website project type is unpopular with developers, perhaps for no other reason than it is different from almost every other project type. The limitations should theoretically make quick-and-dirty website projects more agile, but frankly I don't find the overhead of a Web Application project a concern.
MSDN covers the differences between the two here: http://msdn.microsoft.com/en-us/library/aa730880%28VS.80%29.aspx#wapp_topic5
Because they forgot to add the template. That bug was rectified in SP1.
Besides, there are now two types: website + web application. Use the latter if you can, because website projects don't offer installers.