shadow-copy

ASP.Net cannot create/shadow copy in PRODUCTION

喜欢而已 提交于 2019-12-03 15:48:31
问题 We've recently updated a fairly large ASP.NET website (~1500th alexa traffic ranking) to use VS2010 and .NET 4.0 running on Windows Server 2008 R2 Since then, when we deploy new versions of the site we occasionally noticed the same error in this post: ASP.Net cannot create/shadow copy The error message is: Cannot create/shadow copy 'xxxx, Version=4.0.4301.26898, Culture=neutral, PublicKeyToken=null' when that file already exists However, unlike in that post, the error is occurring only in our

ASP.Net cannot create/shadow copy in PRODUCTION

穿精又带淫゛_ 提交于 2019-12-03 05:17:34
We've recently updated a fairly large ASP.NET website (~1500th alexa traffic ranking) to use VS2010 and .NET 4.0 running on Windows Server 2008 R2 Since then, when we deploy new versions of the site we occasionally noticed the same error in this post: ASP.Net cannot create/shadow copy The error message is: Cannot create/shadow copy 'xxxx, Version=4.0.4301.26898, Culture=neutral, PublicKeyToken=null' when that file already exists However, unlike in that post, the error is occurring only in our production environments & only on some servers. After we ship a new version of the code, we recycle

Creating a shadow copy using the “Backup” context in a PowerShell

一世执手 提交于 2019-12-02 20:09:45
I am in the process of writing a PowerShell script for backing up a windows computer using rsync. To this end, I am attempting to use WMI from said script to create a non-persistent Shadow copy with writer participation (as is apparently recommended for backups). I found out from another question ( Accessing Volume Shadow Copy (VSS) Snapshots from powershell ) a way to create a shadow copy in general, but the example given there uses "ClientAccessible" as the context parameter, which result in the creation of a persistent Shadow Copy, without writer participation. While searching for a

AppDomain shadow copying not working (original assemblies locked)

喜你入骨 提交于 2019-12-01 09:19:48
Here's a small class I'm using to probe for a list of available plugins: internal static class PluginDirectoryLoader { public static PluginInfo[] ListPlugins(string path) { var name = Path.GetFileName(path); var setup = new AppDomainSetup { ApplicationBase = path, ShadowCopyFiles = "true" }; var appdomain = AppDomain.CreateDomain("PluginDirectoryLoader." + name, null, setup); var exts = (IServerExtensionDiscovery)appdomain.CreateInstanceAndUnwrap("ServerX.Common", "ServerX.Common.ServerExtensionDiscovery"); PluginInfo[] plugins = null; try { plugins = exts.ListPlugins(); // <-- BREAK HERE }

Volume Shadow Copy (VSS)

烈酒焚心 提交于 2019-12-01 07:47:03
问题 Can anyone clarify an issue? I'm using the VSS API (C++ using VSS2008 and the latest SDK running on XP SP3) in a home-brew backup utility*. THe VSS snapshot operations work fine for folder that have no subfolders - i.e. my email and SQL server volumes. However when I take a snapshot of a folder that does contain subfolders, the nested structure is 'flattened' in the snapshot - all sub-directories cease to exist. So here is the question: I am aware that support for VSS on XP is a bit limited

AppDomain shadow copying not working (original assemblies locked)

北城余情 提交于 2019-12-01 06:21:57
问题 Here's a small class I'm using to probe for a list of available plugins: internal static class PluginDirectoryLoader { public static PluginInfo[] ListPlugins(string path) { var name = Path.GetFileName(path); var setup = new AppDomainSetup { ApplicationBase = path, ShadowCopyFiles = "true" }; var appdomain = AppDomain.CreateDomain("PluginDirectoryLoader." + name, null, setup); var exts = (IServerExtensionDiscovery)appdomain.CreateInstanceAndUnwrap("ServerX.Common", "ServerX.Common

Opening a file's Shadow Copy if the current copy is in use

我只是一个虾纸丫 提交于 2019-12-01 04:19:57
I'm trying to backup files on a server, but some of them are in use and cannot be opened. Instead, I'd like to open their shadow copy if the current copy is in use. How can I do this? For reference, I'm using C# .net 3.5. This question is quite old already, so my answer might not be of much use to you, but SO being a Q&A site maybe it still helps someone else. I can't / don't want to put down the entire implementation, but the procedure is goes something like this: You create a Volume Shadow Copy via the Volume Shadow Service Provider for the drive where your file to be read is located(this is

Opening a file's Shadow Copy if the current copy is in use

断了今生、忘了曾经 提交于 2019-12-01 01:13:53
问题 I'm trying to backup files on a server, but some of them are in use and cannot be opened. Instead, I'd like to open their shadow copy if the current copy is in use. How can I do this? For reference, I'm using C# .net 3.5. 回答1: This question is quite old already, so my answer might not be of much use to you, but SO being a Q&A site maybe it still helps someone else. I can't / don't want to put down the entire implementation, but the procedure is goes something like this: You create a Volume

What is the right way to set shadow copying for the default AppDomain

怎甘沉沦 提交于 2019-11-30 04:00:27
Relating to Can I make the default AppDomain use shadow copies of certain assemblies? , it describes a working solution to activate shadow copying within the default AppDomain for a specific directory. Basically it says to use these simple methods: AppDomain.CurrentDomain.SetShadowCopyPath(aDirectory); AppDomain.CurrentDomain.SetShadowCopyFiles(); But because the methods used here are marked as obsolete I was wondering what is now the correct way to accomplish the same. The warning message hints to: Please investigate the use of AppDomainSetup.ShadowCopyDirectories instead An AppDomain has a

Help needed with unloading .DLL's from AppDomain - Still not working even with ShadowCopy

有些话、适合烂在心里 提交于 2019-11-28 08:57:36
问题 I am trying to do the following. App A is the "mother app". It stays open. App B is just a .DLL where I write some classes that are derived from an interface specified in App A. Then, from App A, I will "import" classes from App B and run methods within them. I want to be able to dynamically change App B (change code and recompile) and use the new code in App A. I have a post-compile command in App B that copies the new .DLL to the App A directory. App A creates a new AppDomain and uses