There are all sorts of different inline tags, and I haven’t found a place that explains them all in one place, so here is the quick and dirty…
Naspinski – Inline ASP.Net tags… sorting them all out (<%$, <%=, <%, <%#, etc.)
Some development in .NET, Angular, TypeScript, CSS, and also something completely different
There are all sorts of different inline tags, and I haven’t found a place that explains them all in one place, so here is the quick and dirty…
Naspinski – Inline ASP.Net tags… sorting them all out (<%$, <%=, <%, <%#, etc.)
At Mix08, the Silverlight 2 Poster was a hot item given out in many of the session. If you didn’t get yours or if you couldn’t make it, you can feel free to download and print your own!
Silverlight 2 Developer Poster – Silverlight 2 Developer Poster
This article has cheat sheets for retrieving various bits of ASP.NET runtime information. For each bit of info, there is:
* A code snippet for retrieving it in a page, with a link to MSDN
* Description, sometimes explanation
* The value for the live ASP.NET app backing this site”
ASP.NET Runtime Cheat Sheet – HttpRequest, HttpRuntime, AppDomain and friends
In no particular order, here are the top ten things I’ve learned to pay attention to when dealing with production ASP.NET applications. Hopefully they will help you save you some time and headaches. As always, your thoughts and additions are welcome.
Daptivate & by Kyle Beyer – Top 10 Best Practices for Production ASP.NET Applications
I have a love/hate relationship with the ASP.NET Session. It’s such a convenient place to put things, but when you start putting applications into production there are a number of less-than-obvious edge cases that can come up and bite you.
Most often the Session is used when managing state over a long process like a multi-step wizard or questionnaire. However, when people use the Session, they often lean on it a little. They’ll bake it into their design so deep that when it doesn’t work, they’re screwed. That’s not to say they shouldn’t be able to lean on it, I’m just saying that there’s a lot of things going on with Session (not just on ASP.NET, but other frameworks as well) in order to get it to look seamless.
Scott Hanselman’s Computer Zen – Troubleshooting Expired ASP.NET Session State and Your Options
Log the actions of your applications is very important especially when you develop new features or develop very difficult logical business.
But it is also important when users use your applications to understand the critical issues or problems.
To implement quickly the log operations Apache developed an opensource library for .Net developers.
Emanuele’s Blog: Log4net: simple way to use in your Asp.net application
Matt Berseth explains how to create an Outlook like navigation pane in ASP.Net with a combination of an Accordion Ajax Control and the ListView control.
Nice example of how the new Ajax controls in the ASP.NET Ajax Control Toolkit can extend the user experience of regular ASP.Net applications with a minimum of code.
One of the designers on our UI team requested a screen mockup with a page layout that is similar to your typical email client. The page is divided vertically into 2 panes. The left pane contains a 2 level hierarchy of categories and subcategories. As the user selects different subcategories the designer wants the right pane’s content to be updated with the corresponding information. Just like Outlook, the designer wants the subcategories to be displayed within expanding and collapsing panels.
Matt Berseth: Creating an Outlook Navigation Bar using the ListView and Accordion Controls
Last week I gave a presentation on mock objects for Software Professionals of Alaska. Once the PowerPointy hand-waving was out of the way, I illustrated the concepts with code examples using Rhino Mocks. I thought I was well-versed in Rhino Mocks before I started, but in the process of preparing the presentation I realized there was a lot that I didn’t know or had forgotten. So I distilled all the main facts and features down into a 3-page quick reference of tables and example usage. You might argue that 3 pages makes it a ‘slow reference,’ but regardless I still think it’s useful to see all the basics stripped down to the bare minimum. Much of the content came from the Rhino Mocks Documentation Wiki, so look there first if you need more details on a particular feature.
For a (web-)project I am working on, I needed to copy the content of 1 website to a sub-folder of another website after the project was built. This enables the 2 projects being separately developed and deployed, but also allows the one project being deployed as a sub-site of the other one. Got it? 🙂
This is how I did this:
In the project file of the sub-project:
<PropertyGroup>
<MyOutputFolder>C:ProjectOutputFolder</MyOutputFolder>
<OutputSubFolder>SubFolder</OutputSubFolder>
</PropertyGroup>
<ItemGroup>
<MyCopyItems Include="$(MSBuildProjectDirectory)***.aspx" />
<MyCopyItems Include="$(MSBuildProjectDirectory)***.htm?" />
<MyCopyItems Include="$(MSBuildProjectDirectory)***.js" />
<MyCopyItems Include="$(MSBuildProjectDirectory)***.gif" />
<MyCopyItems Include="$(MSBuildProjectDirectory)***.jp?g" />
<MyCopyItems Include="$(MSBuildProjectDirectory)***.png" />
<MyCopyBin Include="$(MSBuildProjectDirectory)bin***.dll" />
</ItemGroup>
<Target Name="MyPostBuildTarget">
<Copy SourceFiles="@(MyCopyItems)"
DestinationFiles="@(MyCopyItems->'$(MyOutputFolder)$(OutputSubFolder)%(RecursiveDir)%(Filename)%(Extension)')" />
<Copy SourceFiles="@(MyCopyBin)"
DestinationFolder="$(MyOutputFolder)bin" />
</Target>
<BuildDependsOn>$(BuildDependsOn);MyPostBuildTarget</BuildDependsOn>
This gives something like:
<!-- Copy project output to defined folder -->
<PropertyGroup>
<BuildDependsOn>$(BuildDependsOn);MyPostBuildTarget</BuildDependsOn>
<MyOutputFolder>C:ProjectOutputFolder</MyOutputFolder>
<OutputSubFolder>SubFolder</OutputSubFolder>
</PropertyGroup>
<ItemGroup>
<MyCopyItems Include="$(MSBuildProjectDirectory)***.aspx" />
<MyCopyItems Include="$(MSBuildProjectDirectory)***.htm?" />
<MyCopyItems Include="$(MSBuildProjectDirectory)***.js" />
<MyCopyItems Include="$(MSBuildProjectDirectory)***.gif" />
<MyCopyItems Include="$(MSBuildProjectDirectory)***.jp?g" />
<MyCopyItems Include="$(MSBuildProjectDirectory)***.png" />
<mycopybin include="$(MSBuildProjectDirectory)bin***.dll" />
</ItemGroup>
<Target Name="MyPostBuildTarget">
<Copy SourceFiles="@(MyCopyItems)"
DestinationFiles="@(MyCopyItems->'$(MyOutputFolder)$(OutputSubFolder)%(RecursiveDir)%(Filename)%(Extension)')" />
<Copy SourceFiles="@(MyCopyBin)"
DestinationFolder="$(MyOutputFolder)bin" />
</Target>
Some references on copying project files with MSBuild:
MSDN MSBuild Reference – Copy Task
Channel 9 Wiki: Copy Built Output Of A Visual Studio Project
SharpDevelop Community – Copy config post build
How To: Insert Custom Process at Specific Points During Build
How To: Add Custom Process at Specific Points During Build (Method #2)
Update: Unlike in C#, in VB.Net the subfolders are not taken into account with the namespace. So the example above in point 10 will be: Namespace + filename
.NET Framework Developer’s Guide:
Design Guidelines for Developing Class Libraries
.NET Framework General Reference:
Design Guidelines for Class Library Developers
The MYSQLWrapper Class is a small and simple to use solution for accessing serverside MySQL Databases at a standard webspace that supports php and mysql.
I thought it would be useful because many of you have got those cheep php/mysql supported sites and want to use data at client side.
SQL queries and non query commands proceed as follows:
- The client side c# programm passes the needed sql command to the serversided script using http request.
- The serversided script performs sql statement an returns the result, if there is any, back to the client
- Now the client parses returned data and creates a Resultset that behaves simliar to the sqlDataReader
The Code Project – C# MYSQLWrapper Class and PHPWrapper-Script
Powered by ScribeFire.