Tem 27 2009

How can I use ampersand in AppSettings value - app config file

Category: ASP.NETLatif @ 00:28


If you want to put an & (ampersand) character into the value attribute of a key in the appSettings part of the XML .config file(web.config, app.config etc.)

Let's say, you have param like following, (The error will occur if you use like this)


    <add key="MyUrl" value="http://localhost:8080/mysite/summarize?name=testPDF&format=pdf"  />


Solution : 


    <add key="MyUrl" value="http://localhost:8080/mysite/summarize?name=testPDF&amp;format=pdf"  />


use &amp; instead of &

Cause :

It is because of XML rules that the & character is the token for beginning of a reference. For more information http://www.w3schools.com/xml/xml_cdata.asp

 tot ziens...


Tags: ,

Tem 14 2009

IsPostBack was always false after installing .NET Framework 3.5 SP1

Category: .Net frameworksLatif @ 02:19


 After installing .NET 3.5 SP1, I realized some problems on my old project which has written on framework 2.0.

 My observations/symptoms on the project-login form:

  • IsPostBack was always false
  • İmagebutton click event not firing
  • I could not login the system

     After 2 days searching  ,luckily I stumbled upon following page. Thanks god :) http://blogs.msdn.com/tess/archive/2009/04/14/validation-of-viewstate-mac-failed-after-installing-net-3-5-sp1.aspx?CommentPosted=true#commentmessage



 There was a form tag in the Login.aspx. Pay attention to action="Default.aspx" (this was the problem)

<form id="form1" method="post" action="Default.aspx" runat="server">

 This problem may occur if your page(in this case Login.aspx) and  form action property(Default.aspx) are different.

 Reason :

      This occurs after installing SP1 for .NET 3.5 is because prior to this service pack, the action property was ignored.  Now that it is no longer ignored.It will work properly. I mean, this is not a bug, it’s a feature...


       Remove the form-action property or change it to post correct page(in this case Login.aspx).

 References :




See you soon....



Tem 11 2009

Choosing between ADO.NET Entity Framework and LINQ to SQL

Category: Entity framework | LINQLatif @ 17:55


       I just would like to share the information I have found from Wriju's BLOG. I want to copy and paste here to share with you. You can find some part of his observation about topic below.

Why I should use Entity Framework?

Ø       It simplifies the data access and allows me to create conceptual model required for my business.

Ø       EF allows you to handle Many to Many relationship without extra join.

Ø       Map related tables into single entity to reduce code complexity.

Ø       Strong inheritance supports for (Table per hierarchy, subclass and concrete type)

Ø       Consolidation for complex object is very easy.

Ø       It has powerful query mechanism through EntitySQL. For them who do not like LINQ you can use EntityClient provider with EntitySQL.

Ø       You can expose your modeled data through ADO.NET Data Services (Astoria).

Ø       Database independent and based on standard ADO.NET Providers.

Ø       There are many third party providers currently available.

o        Devart offers provider for Oracle, MySQL and PostgreSQL

o        Phoenix Software Solution offers EF provider for SQLite.

o        Npgsql offers another provider for PostgreSQL.   

o        OpenLink Software offers a very wide range of support for Oracle (versions 7.x to 11.x), Microsoft SQL Server (6.x to 2005), IBM DB2 , Sybase (4.2 to 12.x+), IBM Informix (5.x to 11.x), Ingres (6.4 to 9.x), Progress (7.x to 10.x), MySQL, PostgreSQL, and Firebird 

o        Sybase SQL Anywhere provides support for SQL Anywhere.

o        IBM natively supports databases like DB2, Informix and U2.

Ø       <TODO: will add few more as and when come across>



At the end of the story I still feel good about LINQ to SQL when it comes to smaller applications with less complexity. Entity Framework is capable of handling large enterprise applications and will have more power in v2 (in .NET 4.0). So if you are targeting your application for multiple databases the L2S is not the right choice for you.

My vote is for ADO.NET Entity Framework. You will enjoy with the conceptual model and Astoria.  

Reference: http://blogs.msdn.com/wriju/archive/2009/03/08/choosing-between-ado-net-entity-framework-and-linq-to-entity.aspx?CommentPosted=true#commentmessage

Till later..

Tags: ,

Tem 11 2009

Removing Entity in Designer leaves references in XML - missing delete functionality in ADO.NET Entity Data Model Designer

Category: Entity frameworkLatif @ 15:07


         When I deleted table(entity) on the designer(edmx), I have found that all the reference about entity ,I have deleted, in XML file remain. And also we cannot add same entity to the designer without doing workaround below,


         We have to delete all the references by hand. Only by this workaround(I cannot say it is a solution), we will be able to add same entity to the designer again.

Then I thought that the ADO.NET Entity Data Model Designer is still in its infancy. it is really big missing feature so I hope Microsoft will repair this big issue in a Hotfix at the earliest.

And I have found some discussions on internet and one of them is :


But I could not see any tangible solution.

See you again..


Tags: ,

Tem 10 2009

Cannot start SQL Server service + SQL Server 2005 Error 3417

Category: SQL Server 2005Latif @ 22:57


When I try to start the Sql Server (MSSQLSERVER) or  Sql Server (SQLEXPRESS) services, get the following error :

Windows could not start the SQL Server (MSSQLSERVER) on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 3417.

After that, I looked at eventvwr. This is the error.

The file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\modellog.ldf" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.


Go to the folder C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\ and select all the files

and right click advanced, uncheck, “Compress contents to save disk space”.

That`s it,piece of cake. Now you can start the services. Try it.

See you...



Tem 10 2009

Debugging problem after installing Visual Studio 2008 SP1

Category: ASP.NETLatif @ 14:38


If you cannot debug after installing Visual Studio 2008 SP1, try to download and setup following link.


I encountered this problem today. After installing that hotfix, it is solved.

see you soon...

Tags: ,