Skip to main content

App_Code Directory (Combining C#.NET and VB.NET)



The App_Code Directory:

bear in mind that any (repeat, any) access to the App_Code folder conducted via HTTP is monitored and blocked by the aforementioned ASP.NET ISAPI fillter.

Note that all class files in the App_Code folder, or in a child folder, must be written in the same language—be it Visual Basic .NET or C#

Your class files in subfolders and add some entries to the con.guration .le to tell the build system to create distinct assemblies—one per language.

<configuration>
<system.web>
<compilation>
<codeSubDirectories>
<add directoryName=”VB” />
<add directoryName=”CS” />
</codeSubDirectories>
</compilation>
</system.web>
</configuration>

the <codeSubDirectories> section is valid only if it is set in the web.con.g .le in the
application root.

The App_Code directory can also contain XSD .les, like those generated for typed
DataSets. An XSD .le represents the strongly typed schema of a table of data.
Labels:

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...
Post a Comment
Continue Reading »

Concept of App Domain in .Net

Creating Application Domains: Application domain is just like process, provides separate memory space, and isolates from other code. But it’s quite light weight. It also provides the following advantages: 1-       Reliability : If a domain crashes, it can be unloaded. Hence doesn’t affect the other assemblies. 2-       Efficiency : Loading all assemblies in one domain can be cumbersome and can make the process heavy but Appdomains are efficient in this manner. Important properties of AppDomain: ApplicationIdentity , ApplicationTrust , BaseDirectory , CurrentDomain , DomainManager , DomainDirectory , Evidence , FriendlyName , ID , RelativeSearchPath , SetupInformation , ShadowCopyFiles . Important methods of AppDomain: ApplyPolicy , CreateCOMInstanceFrom , CreateDomain , CreateInstance (Assembly). To create an AppDomain: AppDomain adomain = AppDomain.CreateDomain(“D”); To execute an assembly:...
Post a Comment
Continue Reading »

Reflecting Types in .NET

Getting Types:                 Type Object can be obtained:                                 From Assembly class                                 From Module class                                 From instance of an object                                 Using typeof keyword in C#   ...
Post a Comment
Continue Reading »