Skip to content

Commit

Permalink
Update Version
Browse files Browse the repository at this point in the history
  • Loading branch information
cturano committed Jan 6, 2017
1 parent ac5dc9b commit b076260
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 7 deletions.
6 changes: 3 additions & 3 deletions SitecorePackageDeployer/Properties/AssemblyInfo.cs
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@
[assembly: AssemblyConfiguration("")]
[assembly: AssemblyCompany("Hedgehog Development")]
[assembly: AssemblyProduct("Hhogdev.SitecorePackageDeployer")]
[assembly: AssemblyCopyright("Copyright © 2015")]
[assembly: AssemblyCopyright("Copyright © 2015, 2016, 2017")]
[assembly: AssemblyTrademark("")]
[assembly: AssemblyCulture("")]

Expand All @@ -32,5 +32,5 @@
// You can specify all the values or you can default the Build and Revision Numbers
// by using the '*' as shown below:
// [assembly: AssemblyVersion("1.0.*")]
[assembly: AssemblyVersion("1.1.0.0")]
[assembly: AssemblyFileVersion("1.1.0.0")]
[assembly: AssemblyVersion("1.6.0.0")]
[assembly: AssemblyFileVersion("1.6.0.0")]
8 changes: 4 additions & 4 deletions SitecorePackageDeployer/Tasks/InstallPackage.cs
Original file line number Diff line number Diff line change
Expand Up @@ -213,11 +213,11 @@ private void InstallPackages()
{
try
{
//The update package may be locked because the file object hasn't been disposed. Wait for it.
Thread.Sleep(100);
//The update package may be locked because the file object hasn't been disposed. Wait for it.
Thread.Sleep(100);

//I really hate this, but I couldn't find another reliable way to ensure the locked file is closed before I move it.
GC.Collect(2);
//I really hate this, but I couldn't find another reliable way to ensure the locked file is closed before I move it.
GC.Collect(2);
GC.WaitForPendingFinalizers();

File.Move(updatePackageFilename, updatePackageFilename + ".error_" + DateTime.Now.ToString("yyyyMMdd.hhmmss"));
Expand Down

0 comments on commit b076260

Please sign in to comment.