Posts

Step by step: Installing CRM 2011 On-premise and Migrating from Dynamics CRM 4.0 (32 bits, on-premise).

Image
Step by step: Installing CRM 2011 On-premise and Migrating from Dynamics CRM 4.0 (32 bits, on-premise). Hi, I have been experimenting a little bit installing Dynamics CRM 2011 and in particular, migrating from a CRM 4.0 32 bits deployment and decided to share it with here the community, specially to show you how simple is the overall process . Obviously there are complete guides downloadable here by Microsoft but they are sometimes not the best reference when you want to have a rapid and visual overview of the process, specially, about the most typical / simple case. Meaning a case where you have an existing on-premise organization with data + entities customizations and workflows. So, I focused here on copy and pasting screenshots of a migration like that, including some brief comments and in case you need more details, I suggest you refer to installation guide. Let's start. First of all.. Installing CRM 2011 In this case, I run SQL Server, Reporting Services and...

Measuring Page Execution Times for ASP.NET Pages

Measuring Page Execution Times for ASP.NET Pages Abstract - (Technical Article) Someone asked me about the page execution time shown at the bottom of this (and every) page. So I thought I would post an article on how to incorporate a page execution timer in your own ASP.NET pages. It’s fairly simple but requires an understanding of the ASP.NET page life cycle. ( Dominic Pettifer ) Monday 27th November 2006 - 7:57pm Understanding the Page Lifecycle It measures the time taken to render this page to HTML, this includes all back end database access stuff, any user or server controls and their own database access, and data binding of web controls. Also the processing of any client side button clicks or other UI interaction and the server side code that fires in response to those events. Basically almost everything. The ASP.NET page life cycle goes through several stages before HTML is rendered and sent to the client. First the Page.Init event is fired, all controls are in...

Database is in use

Stop Connections to the database without single user and without script... System.Data.SqlClient.SqlError: Exclusive access could not be obtained because the database is in use Error: TITLE: Microsoft SQL Server Management Studio ------------------------------ Restore failed for Server 'ServerName'. (Microsoft.SqlServer.Smo) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.4035.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476 ------------------------------ ADDITIONAL INFORMATION: System.Data.SqlClient.SqlError: Exclusive access could not be obtained because the database is in use. (Microsoft.SqlServer.Smo) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.4035.00&LinkId=20476 ------------------------------ BUTTONS: OK ------------------------------ Solution: 1- Open SQL Management Studio. 2- Mana...

ASP.NET 2.0 Tips and Tricks 4

Locate nested controls easily: Finding controls within a Page's control hierarchy can be painful but if you know how the controls are nested you can use the lesser known "$" shortcut to find controls without having to write recursive code. If you're looking for a great way to recursively find a control (in cases where you don't know the exact control nesting) check out my good buddy Michael Palermo's blog entry. The following example shows how to use the DefaultFocus property to set the focus on a textbox that is nested inside of a FormView control. Notice that the "$" is used to delimit the nesting: Name: Text=' ' / > This little trick can also be used on the server-side when calling FindControl(). I blogged about this awhile back if you'd like more details. Here's an example: TextBox tb = this.FindControl("form1$formVw$...

ASP.NET 2.0 Tips and Tricks 3

Set the default button that is triggered when the user hits the enter key: This was a major pain point in ASP.NET 1.1 and required some JavaScript to be written to ensure that when the user hit the enter key that the appropriate button on the form triggered a "click" event on the server-side. Fortunately, you can now use the HtmlForm control's DefaultButton property to set which button should be clicked when the user hits enter. This property is also available on the Panel control in cases where different buttons should be triggered as a user moves into different Panels on a page. ...

ASP.NET 2.0 Tips and Tricks 2

Set the default focus to a control when the page loads: This is another extremely simple thing that can be done without resorting to writing JavaScript. If you only have a single textbox (or two) on a page why should the user have to click in the textbox to start typing? Shouldn't the cursor already be blinking in the textbox so they can type away? Using the DefaultFocus property of the HtmlForm control you can easily do this. ...

ASP.NET 2.0 Tips and Tricks 1

Maintain the position of the scrollbar on postbacks: In ASP.NET 1.1 it was a pain to maintain the position of the scrollbar when doing a postback operation. This was especially true when you had a grid on the page and went to edit a specific row. Instead of staying on the desired row, the page would reload and you'd be placed back at the top and have to scroll down. In ASP.NET 2.0 you can simply add the MaintainScrollPostionOnPostBack attribute to the Page directive: MaintainScrollPositionOnPostback="true" AutoEventWireup="true" CodeFile="..." Inherits="..." % >