For example:

This works

The path is c:\ccnetworkdir\kudu\kudu.FunctionalTests\bin\debug\tests\testrepositories\CloneFromEmptyRepoAndPushShouldDeploy\CloneFromEmptyRepoAndPushShouldDeploy1234

If I make the path 1 character longer, git will be corrupted:

You can notice that the branch name has become "((ref: re...))" instead of (master).

Background:

We have a bunch of tests written in Javascript using QUnit and checked in to Github.  We'd like to set up a continuous integration system that pull the code from Github, and run the tests on the browsers/devices that we are interested in.  After some research, we decided to start with the following:

• Jenkins for its integration of  Git plug-ins.
• TestSwarm 
• Nice integration with Qunit and be able to integrate into Jenkins as a build step. 
• Natual support for multiple browsers and devices
• We tried to stay on Windows Server as much as possible.

Experience:

TestSwarm

TestSwarm is not designed to be installed on traditional Windows servers natually.  However, since it simply uses php + MySql + javascript and some Apache RewriteRules, it's pretty easy to run it on Windows Server as well.  Here's what I did:

• Install Apache for Windows, MySql and PHP.
• Follow the instruction of TestSwarm's wiki on Github: https://github.com/jquery/testswarm , including set up mysql database, setting config.ini and .htaccess.  I just ignored item #5 regarding cronjob.
• Go to https://<serverName>/<swarmPath> (such as https://localhost/testswarm/ ) and register a new user.  Go to the MySql database and find token value of the user just created in the "Users" table, which is needed later to add new jobs
• To test if it works, open the testswarm page, log in, and open this page: https://localhost/testswarm/?state=addjob; *** NOTE The trailing ";" is very important.  Otherwise, you'll get a "Incorrect user name or Auth Token".  I was able to repro this on testswarm's website.  It seems this manual page is rarely used.  It's more common to add jobs programmatically.  Add a job and suite to point to some test page, and go to https://localhost/testswarm/user/<username>  to see the new job added or open https://localhost/testswarm/run/<userName> to run the actual test

Jenkins

Installation

• Download Jenkins from its official site https://jenkins-ci.org/
• Install Java
• java -jar jenkins.war

Configuration

1. Install plug-ins
• Open https://localhost:8080 from browser.  Click "Manage Jenkins", then "Manage Plugins".
• Add "Jenkins Git plugin", "Github Plugin", "Jenkins MS build Plugin" from Available Plugins
• I aslo need the Jenkins-TestSwarm plugin, which cannot be found in the available plugins list of Jenkins.  The Jenkins-Testswarm project is on Github https://github.com/appendto/jenkins-testswarm .  It contains a testswarmbuilder.hpi, which can be installed to Jenkins plugins (advance).  Ideally, everything should just work now.  It's true if you will not use any variables in your Testswarm settings.  It's not true in our case.  We'd like to deploy each commit to a new VDir, something like https://myserver/myproject/%Build_Number%/mytestpage1.html .  We also wanted to customize the testswarm job title to show the Git commit number, which is available in Jenkins Git plugin as an environment variable: %GIT_COMMIT%   However, there's a bug in Jenkins that does not replace the variables in settings with actualy environment variables.  I have filed an issue https://issues.jenkins-ci.org/browse/JENKINS-11451 to track the issue.   My fix is at https://github.com/xusun/jenkins/commit/b8dee2c710637e718290f93c31d3854099d2d157#comments   To workaround it, I did not recompile the entire Jenkins project.  Instead, I downloaded the testswarmbuilder plugin and replaced the reproMacro calls with my fixed version.  Rebuild the hpi and reinstall it to Jenkins.  That fixed the variable issue.
2. Config system ("Manage Jenkins" => "Configure System")
• Under Git section, set up "Path to Git Executable".  This points to the full path to Git.exe
• Under Git Plugin, input your names on Git and email.
• Email Notification: it seems Jenkins has problems on authentications to exchange smtp servers.  see Jenkins' issue 3983.https://issues.jenkins-ci.org/browse/JENKINS-3983.  There are two workaround that I tried sucessfully:
• use smtp.gmail.com as smtp server
• config your local IIS to act as a smtp relay server.  see this msdn for details.  In the local SMTP server, you can set up the authentication credentials used for relay.  In this way, you don't need authentication with Jenkins. Note that even you have IIS7.0, this smtp server is managed in IIS6 management portal.

Add Jobs

Our workflow is like this: [Sombody checkin on Github] - > [Jenkins pull from Github ] -> [msbuild our solution] -> [msdeploy the websites to our IIS/Asp.net server] -> [Add test jobs to TestSwarm] -> [TestSwarm executes and return results] -> [Jenkins build Success/Fail] -> [Email groups]

The following might need to be mentioned:

1. Config the Git repository: In the help of Jenkins, you can set up the git url as https://... or git://... or ssh://.   Since we have a private repo, the easiest way is to use ssh with a no-password key in the CI machine.
2. Build triggers.  It's hard for us to define a Git callback proxy.  So, we just simply use Poll SCM per minute: "* * * * *".
3. Deploy to IIS server.
1. We would like to keep some build history for reference and possible issue investigations.  But we also wanted to keep the IIS server as clean as possible.  So, before deployment of a new build to IIS, we simply query the server for existing deployed vDirs and delete those that is older than n builds.  Since we use the jenkins build number as the vDir name, it's easy to simply write a batch file to call msdeploy to do this.  Here's the code, (although I have to admit that I'm not good at batch programming).  Here we used Jenkins environment variables %BUILD_NUMBER%

@echo off
 setlocal ENABLEDELAYEDEXPANSION
 
 IF /I '%1' == '' GOTO usage
 
 SET TARGET=%1
 
 SET KEEP=10
 ECHO CLEANING APP %KEEP% LESS THAN %BUILD_NUMBER%
 set cmd="msdeploy -verb:dump -source:iisapp="Default Web Site\MyProject",computername=%TARGET%"
 
 
 FOR /f "tokens=1-5 delims=\\" %%G IN ('%cmd%') DO (
 IF "%%J"=="" ( 
 IF "%%H"=="upshot" ( 
 IF NOT "%%I"=="" ( 
 set /a test=%%I
 
 IF !test! GTR 0 (
 set /a commit=%BUILD_NUMBER% - !test!
 IF !commit! GTR %KEEP% (
 echo msdeploy -verb:delete -dest:iisapp="Default Web Site\MyProject\!test!",computername=%TARGET%
 msdeploy -verb:delete -dest:iisapp="Default Web Site\MyProject\!test!",computername=%TARGET%
 )
 ) 
 )
 )
 )
 )
 
 GOTO end
 
 :usage
 ECHO.
 ECHO CleanOldVDirs [TARGET_COMPUTER_NAME]
 GOTO end
 
 :end
 EXIT

 b. deploy script is even simpler:

@echo off
 setlocal ENABLEDELAYEDEXPANSION
 
 IF /I '%1' == '' GOTO usage
 
 SET TARGET=%1
 
 CALL msdeploy -verb:sync -source:iisapp="%WORKSPACE%\test\MyProj.Test" -dest:iisapp="Default Web Site\MyProject\%BUILD_NUMBER%",computername=%TARGET%
 REM ...
 REM OTHER DIRS TO DEPLOY 
 GOTO end
 
 :usage
 ECHO.
 ECHO CreateNewVDir [TARGET_COMPUTER_NAME]
 GOTO end
 
 :end
 EXIT

4.TestSwarm integration:

• we use Git commit id as the TestSwarm job title:  Commit # <a href="https://github.com/xxx/MyProj.js/commit/%GIT_COMMIT%">%GIT_COMMIT%</a>
• Auth token can be found in the MySql database on the TestSwarm machine

That's it.   Final tip would be that the Testswarm machine may need some config update  on the php.config to make the server on production state.   Otherwise, the php error log may heavily slow down the server and cause timeout on TestSwarm jobs.

var endpoints = MetadataResolver.Resolve(typeof(ICityService), new EndpointAddress("https://xxx/CityService.svc"));

Instead, it should point to the wsdl and better explicitly specify it's using HttpGet

var endpoints = MetadataResolver.Resolve(typeof(ICityService), new Uri("https://xxx/CityService.svc?wsdl"),  MetadataExchangeClientMode.HttpGet );

2. In the Web project, add a reference to %ProgramFiles(x86)%\Microsoft SDKs\RIA Services\v1.0\Toolkit\Libraries\Server\Microsoft.ServiceModel.DomainServices.Hosting.dll

3. Edit the Web.config and add the following to the <configuration> section

<configuration>
  <configSections>
    <sectionGroup name="system.serviceModel">
            <section name="domainServices" type="System.ServiceModel.DomainServices.Hosting.DomainServicesSection, System.ServiceModel.DomainServices.Hosting, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" allowDefinition="MachineToApplication" requirePermission="false" />
    </sectionGroup>
  </configSections> ...

 and the following to the <system.serviceModel> section:

 <system.serviceModel>
        <serviceHostingEnvironment aspNetCompatibilityEnabled="true"
            multipleSiteBindingsEnabled="true" />
      <domainServices>
        <endpoints>
          <add name="JSON" type="Microsoft.ServiceModel.DomainServices.Hosting.JsonEndpointFactory, Microsoft.ServiceModel.DomainServices.Hosting, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
        </endpoints>
      </domainServices>

Done.  Now you can open the json endpoint like this: https://localhost:27525/SilverlightApplication1-Web-DomainService1.svc/json

The endpoints node also support other actions, such as "add" and "remove".  You can also add other endpoints, such as soap and xmljson,  in the same way or remove the default "binary" endpoint.

Here's how I do it:

1. Setting up a new Silverlight Application with RiaServices enabled. 
• Creat new Silvelirght Application.
• In Server project, add a new Ado.NET Entity Data Model
• In Servers Explorer, connect to my SQL Server, Northwind Database, Check Customer and Order tables.
• Build Server Project
• Add a new DomainServices class.  Select both Customer and Order tables in the Wizard and Enable editing.
• Build the client project
2.  If you are using SL4, you would have the Drag/Drp from Data Source feature enabled in the client, where you can drag the data model into the UI.  Here I picked the Order Entity and use ComboBox for displaying the Customer property: 

   

3. Change the Order type to  Detail and drag it to the MainPage.xaml designer.  The Order Entity is displayed as a Grid where each property is a displayed in a column.  Here I'm only demonstrating the setting up of the ComboBox.  In real life, you might want a DataForm hooked up with the Order. The designer will automatically create a DomainDataSource and hook up the DataContext of the Grid to the DomainDataSource:
4. Then I change the first TextBox that was bound to CustomerID to a ComboBox.  Here we need to worry about 3 bindings: ItemsSource, SelectedItem and DisplayMemberPath
5. Ideally, ItemsSource should contain all the customers, so that users could select from.  These customers instance should come from the same NorthwindCatalog DomainContext as used in the DomainDataSource.  I set this up by creating a StaticResource that expose the EntitySet<Customer> of the NorthwindCatalog in client.  Here, I used a singleton DomainContext (NorthwindCatalog) that is shared by both DomainDataSource and my StaticResource.
6. I created a new Class   EntityProvider that contains a static NorthwindCatalog:



7. Then I commented out the DomainContext definition in the DomainDataSource and in the Page constructor I set its DomainContext to the static one







8. Now we can just set the ComboBox.ItemsSource to this static resource
9. Next, we can just set the SelectedItem binding to the Custom property since the DataContext is Order
10. By default, it would display the id.  If we'd like to be more friendly, we can set the DisplayMemberPath to one of the properties of Customer, for example, the ContactName
11. Here's the final ComboBox:



12. Final result when running:

(Courtesy RIA Services QA)

·         Recommended Steps:

o   Create a separate project

o   Add new EDMX models from the current database and let the framework naturally auto-generate all the names first. 

§  Remember to leave this option checked (the default):

o   Change the global names from UI first:

§  Entity Container Name

§  Namespace

§  Custom Tool Namespace

o   Then do a replace from the new model to the old one (Tip: Pick up your favorite diff tool for this). 

§  Some models have clear changes that were easily matched

§  Some models are generated with disordered properties.  In such cases, one has to copy everything and rely on the following steps to update them. (Recommended)

o   Save and try to open the edmx designer

§  If there are some changes not made correctly, VS won’t open the designer and will identify the error.  Fix all errors.

o   Re-Compile the Server project

§  The existing DomainServices classes will show errors for any changed names that were not correct.

§  To further fix the names:

·         Open the EDMX model browser

·         Based on the compiler error messages, check the corresponding name in Entity Types, Associations, EntityContainer.EntitySets, Association Sets and Model.Store Tables and make sure that the new version matches the old ones.

o   After fixing all the errors, the update is completed.

·         Caveats:

o   If possible, consider using the new names and update your DomainServices instead of changing the model.

o   If you have to, let the designer do the right thing for you.  Try NOT touch the edmx file manually, unless you have to. 

https://blogs.msdn.com/seema/archive/2009/01/07/published-the-control-source-code-for-silverlight-2-runtime-sdk.aspx

We’ve just published the sample source code for the Silverlight 2 Controls as shipped in the runtime and the SDK.

Within the RuntimeControls folder, you’ll see a Solution that contains three projects:

1.       SilverlightControls – One can edit the source and default control templates of the controls in order to build a DLL containing custom versions of the controls.

2.       Controls Sample – One can take the SilverlightControls DLL from #1 and include it in a project such as this. If you press F5, this app will launch displaying the controls created in #1.

3.       System.Windows.Design – This project is here largely for reference, it shows how to build a Design dll for VisualStudio and Expression Blend such that your custom controls would display within the toolbox.

Disclaimer: Note that we did take a small amount of changes in the Runtime Controls to get the project to properly build outside of our internal build environment.

这里列出一些常用的设置Image 相对路径的几种方法:

假设我有这样一个solution,包括: MyImageLibrary,其中包含一个文件夹"Images\MyImage1.png"; MyLoadImage是我的Silverlight Application里面也有一个Images\MyImage2.png, 页面中有一Image控件来分别显示这两个图片 

那么有如下几种选择:

1. Build Action="Resource", Copy To OutPut Directory = "Do not copy".

这时如果需要用另一个项目中的Image,那么需要这样设置Image路径

xaml: <Image Source="/MyImageLibrary;component/Images/MyImage1.png" />

code: myImage.Source = new BitmapImage(new Uri("/MyImageLibrary;component/Images/MyImage1.png", UriKind.Relative));

这个Uri有如下3部分：

• /MyImageLibrary 是Image所在的Assembly的名字，前面的"/"是必须的。
• ";component/"是Assembly名字和在此Assembly下具体路径之间的分隔符，必须要有。
• "Images/MyImage1.png" 就是所在Assembly中的路径啦。

此时图片是作为资源被嵌入进Assembly的. 如果用Reflector 打开MyImageLibrary.dll，就能够找到这个资源：

这是Image在另一个assembly的时候的用法，如果在同一个项目下，那就可以直接这样用：

<Image Source="Images/MyImage2.png"/>

2. Build Action = "Content", Copy To OutPut Directory = "Do not copy".

这种情况，如果图片在另一个Project中，那是没有办法获得的。只有在同一个Project中的时候,才能够被找到，因为这种设置会把Image嵌入.xap中.如果打开生成的xap,会看到如下:

可以看到只有同一个Project中的Image作为Content嵌入到xap中。

这时的用法就是

<Image Source="Images/MyImage2.png"/>

3.Build Action = "None", Copy To OutPut Directory = "Copy Always".

如果不希望图片被压进Xap文件，而是用户调用的时候再动态Load,那可以用这种方法。这种方法图片会被复制到 xap所在路径下,路径依然是 Images\MyImage1.png, Images\MyImage2.png.

使用方法如前<Image Source="Images/MyImage1.png" /> 或<Image Source="Images/MyImage2.png"/>

遇到图片加载错误时，应该先检查选用的是那种方法，然后再检查图片是否被正确放在所期望的地方,dll/xap/路径 中。

其他常见的原因还包括：用绝对路径的时候要注意是否是Cross-scheme, 比如如果你的项目要从加载位于 https://www.mydomain.com/Myimage.png的图片，但是如果你Debug是在浏览器中打开的是file://C:/MyProject/..那就属于是cross-scheme (File vs. Http),这时会有Security错误产生，解决方法就是用一个ASP.net website 作为起始工程，然后加入Silverlight 工程。

这个版本的发布其实令我个人感觉很高兴,因为这让人看到了Microsoft在对用户的反馈方面速度的提高,不再是一味的等待大的发布,而是通过各种更加灵活的手段迅速解决已发现的用户面临的各种问题.我真的希望这个模式会让我们的产品更加具有竞争力.

下面是这个Release所修正的Bug:

Silverlight 2 DataGrid December 2008 Release

We have just uploaded a new version of the DataGrid that includes a number of bug fixes and a few behavioral breaking changes from the version that shipped with Silverlight 2.  Please take the time to read through and understand all of the changes before you decide to upgrade your DataGrid.  Following this list of changes is a set of instructions on how to start using the new version.

Breaking Changes

An application that uses the DataGrid will still compile but will no longer work as expected if it was dependent on any of the following behaviors.

1.       FrozenColumnCount now takes hidden columns into account.  Previously, only the first columns with Visibility set to Visible were included in the range of frozen columns.  A column with Visibility set to Collapsed can now be considered frozen even though it isn’t visible.  This is to ensure that a column’s DisplayIndex corresponds with the DataGrid’s FrozenColumnCount (i.e. if FrozenColumnCount == 3, columns with DisplayIndex < 3 are considered frozen).

2.       The DataGrid’s current cell is now kept in sync with an ICollectionView’s notion of currency.  Moving the current position or changing the current item of an ICollectionView will now move the current cell and selected item of a DataGrid, and vice versa.  For this to work, the DataGrid’s ItemsSource must be set to a collection that fully implements ICollectionView.

3.       A developer can now programmatically reorder a non-frozen column to the frozen column range (and vice versa) by changing a column’s DisplayIndex.  The DataGrid used to throw an exception in these cases.  An end-user, however, is still unable to do this through the UI by dragging column headers.

Bugs Fixed

The following is a list of bugs fixed in the DataGrid since the version released with Silverlight 2.  If any application had a workaround for these bugs, the workaround is no longer necessary and should be removed.  Its inclusion may cause undesired behavior.

1.       Horizontal Gridlines do not show in FillerColumn

2.       DragIndicator does not show during reorder when DataGrid is placed inside StackPanel

3.       DragIndicatorStyle only exists on the DataGrid level, should also exist at the column level

4.       DataGrid doesn't support a disabled state in the main template
By default, the DataGrid is now grayed out when IsEnabled == false, and includes a new visual state.

5.       EndEdit is called twice
      Any application accounting for IEditableObject.EndEdit accidentally being called twice by the DataGrid will need to be updated. 6.       Able to leave edited DataGrid without ever triggering EndEdit

7.    Changing ItemsSource while in Editing Mode causes Exception to be thrown

8.       Row containing focus disappears after sort or ItemsSource change
Any application working around the “disappearing row” issue by manipulating focus within the DataGrid will no longer need to do so, and should be updated.

9.       ColumnHeader button pressed visualization should match the new Button pressed visualization

10.   SL Designer hits a NullReferenceException while adding an empty HeaderStyle

11.   Cells out of view do not always show up when a resize of the DataGrid forces them in view

12.   AutoSizedRows keep growing even when the rows are recycled

13.   Scrollbar incorrect when ItemsSource changed and DataGrid is on a background Tab

14.   Incorrect VerticalScrollbar when setting ItemsSource on DataGrid inside a Popup

15.   HorizontalContentAlignment does not have any effect on the DataGridColumnHeader

16.   Resizing columns to smaller than column header content removes separator

17.   SelectedItem is not updated at the time when the CurrentCellChanged event is raised

      Any application accounting for the fact that Selection was out of sync at the time the CurrentCellChanged event was raised will need to be updated.  Now the DataGrid will not raise either of the SelectionChanged or CurrentCellChanged events until both selection and currency have been updated.

18.   Sorting or Resetting a CollectionView causes incorrect RemovedItems in SelectionChanged event

19.   ScrollColumnIntoView does not align correctly if there are frozen columns

20.   Reordering a column should only show DragIndicator for valid reorder positions

      The DataGrid will now clip the ColumnHeader’s DragIndicator so that it doesn’t show up when dragging a frozen column over a non-frozen column, and vice versa.

21.   Adding or removing columns within the frozen column range should not throw exception

22.   FrozenColumnCount and the Column’s IsFrozen is getting out of sync when it isn’t visible

23.   Exception thrown when sorting a DataGrid that has a list of nullable ints as its ItemsSource

24.   CellStyle Background property doesn’t work

      Previously, setting the Background property inside of CellStyle had no effect.  Applications with unique CellStyles should ensure that the desired background color is applied.

25.   CellStyle is not applied to Filler Column

26.   Setting a DataGrid style that overwrites the template after the original template has been loaded causes an Argument exception

27.   Cannot hold editing mode when using a DatePicker or ComboBox in editing template

      There was a bug that prevented any editing control that uses a Popup to work correctly in the DataGrid.  As soon as the Popup opened, the DataGrid would lose focus and automatically CommitEdit.  It now tracks focus within a child Popup in order to support DatePicker, ComboBox and any other editing control that opens a Popup.

28.   Double-click required on external Buttons when in editing mode

      A single click on Buttons (or any other control that handles MouseLeftButtonDown) outside of the DataGrid will now register correctly.  Previously, if the user was in editing mode, the first click would CommitEdit and the second click would register on the Button.

29.   Sorting or resetting the ItemsSource does not raise UnloadingRow events

Visit the Silverlight 2 DataGrid December 2008 Release download page and read the installation instructions carefully.  In order to successfully use the new DataGrid you must do the following.

1.       Close all instances of Microsoft Visual Studio.2.       Delete all cached toolbox items by removing all files beginning with "toolbox" from %LocalAppData%\Microsoft\VisualStudio\9.0.