ASP.Net

In one of my projects, I use an ASP.Net MVC site to communicate with Team Foundation Server (TFS) to display metrics/graphs/reports. The site is hosted on the same server that hosts TFS and during publication, it publishes the file Microsoft.TeamFoundation.WorkItemTracking.Client.DataStoreLoader.dll in the bin folder each time, which causes an ASP.Net error because the dll is already on the server.

It is possible in an ASP.Net MVC project to exclude files and directories by creating a .wpp.targets file. This allows you to define the exclusions as well as the source/reason for the exclusion.

As I previously highlighted, an ASP.Net vulnerability can be exploited by malicious individuals. Here is a demo exploiting it on the DotNetNuke platform.

For all those who have ASP.Net sites, all versions included, please pay special attention to this security issue: details on this entry from ScottGu.

VS2010 is now available (Trial, Express and for MSDN subscribers). Scott Hanselman has written an excellent article summarizing all the new features of this new version, now it’s your turn to play!

Rick Strahl saved my day with his post “Making sense of ASP.NET Path” especially the following line:

<script src="<%= Url.Content("~/scripts/new.js") %>" type="text/javascript"></script>

The Orchard Project can now be installed via the Web Platform Installer (WebPI). Just follow the instructions!!

The source files are still available on CodePlex.

The Orchard Project aims to create an application and reusable components using ASP.NET. Additionally, in the short term, it will provide a CMS application based on .NET.

Having tested it several times, it seems very promising, but still too immature to consider using it as my Blog engine. But we’ll see….

The source code is available on CodePlex

If you ever use the Oracle ODP.Net component with SqlDataSource and get the ORA-01036 Illegal variable name/number error, it is mainly due to the fact that your number of parameters does not match the number in your Insert, Update, or Delete query. I had this problem using a ComposedKey with the ASPxDataGridView from DevExpress. You need to remove the ComposedKey field before executing the query.

Here is the conversation on ASP.Net that helped me resolve this issue.