Recognizing #include statements for code inclusion...

[anthony]

Is it possible for JustCode to "follow" #include directives? One coding style I follow is to put the dotNet header statements into an include file and add the #include directive to the top of all my pages. (I know that master pages can provide similar functionality - but I have a lot of code built under this "unique" style).

In those header includes, I have the @Page / Src / @Import etc. And JustCode fails to find the referenced codebehind and therefore my "public" variables.

On every ASPX page:

<!-- #include virtual="/includes/dotNet_Header.inc" -->
<!-- #include virtual="/includes/dotNet_Import.inc" -->

header.inc

<%@ Page Language="C#"
         Inherits="KB.SharedLibrary.SharedCode"
         Src="/bin/lib_shared.cs"
         AutoEventWireUp="true"
         validateRequest="false"
         aspcompat="true" %>

Import.inc

<%@ Import Namespace="KB.SharedLibrary" %>
<%@ Import Namespace="System.Collections"%>
<%@ Import Namespace="System.Collections.Generic"%>
<%@ Import Namespace="System.Data" %>
<%@ Import Namespace="System.IO" %>
<%@ Import Namespace="System.Xml" %>
<%@ Import Namespace="System.Xml.Serialization" %>
<%@ Import Namespace="System.Net" %>
<%@ Import Namespace="System.Net.Mail" %>
<%@ Import Namespace="System.Net.Mime" %>
<%@ Import Namespace="System.Drawing" %>
<%@ Import Namespace="System.Web.UI.HtmlControls" %>

It would reduce all the misstated "errors" because JustCode is not following the #include command and the referenced "Src" attribute for the code-behind page.

Again, I know this is not standard dotNet page construction.

[Zdravko]

Hi,

 Thanks for contacting us.
We will talk about this within the team, but I do not think this idea will be well accepted.
This is the first time that someone is asking such a feature and its priority seems to be very low.
Thanks for the suggestion and have a nice day.

Greetings,
Zdravko
the Telerik team