Hide / Remove Title column from Sharepoint List

Well here we go :

(1)Go to Your list settings on which you want to hide/remove title column.
(2)Go to advanced settings of that list.
(3)Click on yes at very first option. Allow management of content types.
(4)Once you do this, one more setting panel becomes visible in advanced settings options. check out the figure below.

(5)Now click on that Item content Type.
(6)As you can see here you will find all columns are listed along with Title column.
(7)Click on that Title column. you will see a page similar to this.

(8)Select the last radio button which is Hidden.
(9)save all settings and then go back to list and click on new Item and see… now Title column is no more there….

Make sure that you also remove all reference of Title column from views because it is hidden now but still it will be there in views.

change the view and add “Edit (link to edit item)” you will have a button for editing the item.

Visual Studio 2008 extensions for SharePoint (VSeWSS) 1.3 addresses all common SharePoint Developer requests

Microsoft just finished the VSeWSS 1.3 March 2009 CTP which released a couple of days ago. Read about the new features in the release notes and if there’s anything we missed, please tell us.

If you want to see how easy it is to get going with SharePoint Development using VSeWSS, check out Kirk Evans short screecast showing building a Web Part, packaging and deploying it and some of the new features that make workarounds a thing of the past.

If you want to learn SharePoint Development using VSeWSS, check out the hands on labs and training videos at MSSharePointDeveloper.com.

Also released today is a set of 10 new theme projects for VSeWSS. These are individual Visual Studio 2008 projects which when deployed to SharePoint offer fresh new designed themes you can use in your projects.

And Daniel Brown has wrapped these themes into WSP

SecurityException: Requested registry access is not allowed.

If your application needs to use application specific event sources, you
should create them at installation time when administrator privileges are
available. A good approach is to use a .NET installer class, which can be
instantiated by the Windows Installer (if you are using .msi deployment) or
by the InstallUtil.exe system utility.

If you are unable to create event sources at installation time, and you are
in deployment, the administrator should manually create new event source
entry beneath the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\

Note:
You should not grant write permission to the ASP.NET process account (or
any impersonated account if your application uses impersonation) on the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\ registry
key. If you allow write access to this key and the account is compromised,
the attacker can modify any log-related setting, including access control
to the log, for any log on the system.

As you can see, creating event source at HKLM will certainly requires
administrative privilege.

ADO DOTNET Entity Data Model

I am using VS 2008 Sp1 (not beta), when I want to create entity model, the entity model wizard closes with no error, when I choose from Database.

Install

EFB3setupx86 and EFToolsSetupX86, then

1) Open the “Visual Studio 2008 Command Prompt” (with administrator privileges if Vista)
2) devenv /resetskippkgs
3) Close Visual Studio
4) devenv /setup
5) Run Visual Studio

using C# to Replace special characters in XML

We can use the SecurityElement.Escape method to replace the invalid XML characters in a string with their valid XML equivalent [1].

Namespace: System.Security
Assembly: mscorlib (in mscorlib.dll)

I have used the HttpUtility classes UrlEncode and UrlDecode methods to handle cross-site scripting attacks and this also helped me to get rid of the XmlException – “Data at the root level is invalid”.

tagText = SecurityElement.Escape(tagText);

http://msdn.microsoft.com/en-us/library/system.security.securityelement.escape(VS.80).aspx