Area path error when Source and Target Area Paths are different while migrating Work Items from TFS to Azure through VSTS - azure-devops-migration-tools

Below is the structure in source:
Drug Library Editor
Below is the structure in Target:
DaVinci\xx\yy\zz\Drug Library
Below is what I have for the query :
"WIQLQueryBit": "AND [System.WorkItemType] = 'Specification' AND [System.AreaPath] Under 'DaVinci\\xx\\yy\\zz\\Drug Library' ",
Below is the error I get when I am executing the processor, it fails when running the query on the target system to find if the work item has already been migrated:
[07:52:38 DBG] WorkItemQuery: Query: SELECT [System.Id], [System.Tags] FROM WorkItems WHERE [System.TeamProject] = 'DaVinci' AND [System.WorkItemType] = 'Specification' AND [System.AreaPath] Under 'DaVinci\Infusion\Neo\Connectivity\Drug Library' ORDER BY [System.ChangedDate] desc
[07:52:38 DBG] WorkItemQuery: Paramiters: {"TeamProject": "DaVinci"}
[07:52:38 DBG] WorkItemQuery: TeamProject: DaVinci
[07:54:31 INF] Replay all revisions of 748 work items?
[07:54:31 INF] Found target project as Test_Connectivity
[07:54:31 INF] [FilterWorkItemsThatAlreadyExistInTarget] is enabled. Searching for work items that have already been migrated to the target...
[07:54:31 DBG] FilterExistingWorkItems: START |
[07:54:31 DBG] FilterByTarget: Query Execute...
[07:54:31 DBG] WorkItemQuery: ===========GetWorkItems=============
[07:54:31 DBG] WorkItemQuery: TeamProjectCollection: https://dev.azure.com/BD-MMS-Connectivity/
[07:54:31 DBG] WorkItemQuery: Query: SELECT [System.Id], [Custom.TFSID] FROM WorkItems WHERE [System.TeamProject] = 'Test_Connectivity' AND [System.WorkItemType] = 'Specification' AND [System.AreaPath] Under 'DaVinci\Infusion\Neo\Connectivity\Drug Library' ORDER BY [System.ChangedDate] desc
[07:54:31 DBG] WorkItemQuery: Paramiters: {"TeamProject": "Test_Connectivity"}
[07:54:31 DBG] WorkItemQuery: TeamProject: Test_Connectivity
[07:54:31 ERR] Error running query
Microsoft.TeamFoundation.WorkItemTracking.Client.ValidationException: TF51011: The specified area path does not exist. The error is caused by «'DaVinci\Infusion\Neo\Connectivity\Drug Library'».
at Microsoft.TeamFoundation.WorkItemTracking.Client.Query.Initialize(WorkItemStore store, String wiql, IDictionary context, Int32[] ids, Int32[] revs, Boolean dayPrecision)
at Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemStore.Query(String wiql, IDictionary context)
at MigrationTools._EngineV1.Clients.TfsWorkItemQuery.GetWorkItemsFromQuery(TfsWorkItemMigrationClient wiClient) in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.ObjectModel\_EngineV1\Clients\TfsWorkItemQuery.cs:line 40
[07:54:31 FTL] Error while running WorkItemMigration
Microsoft.TeamFoundation.WorkItemTracking.Client.ValidationException: TF51011: The specified area path does not exist. The error is caused by «'DaVinci\Infusion\Neo\Connectivity\Drug Library'».
at Microsoft.TeamFoundation.WorkItemTracking.Client.Query.Initialize(WorkItemStore store, String wiql, IDictionary context, Int32[] ids, Int32[] revs, Boolean dayPrecision)
at Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemStore.Query(String wiql, IDictionary context)
at MigrationTools._EngineV1.Clients.TfsWorkItemQuery.GetWorkItemsFromQuery(TfsWorkItemMigrationClient wiClient) in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.ObjectModel\_EngineV1\Clients\TfsWorkItemQuery.cs:line 72
at MigrationTools._EngineV1.Clients.TfsWorkItemQuery.GetWorkItems() in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.ObjectModel\_EngineV1\Clients\TfsWorkItemQuery.cs:line 28
at MigrationTools._EngineV1.Clients.TfsWorkItemMigrationClient.FilterExistingWorkItems(List`1 sourceWorkItems, TfsWiqlDefinition wiqlDefinition, TfsWorkItemMigrationClient sourceWorkItemMigrationClient) in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.ObjectModel\_EngineV1\Clients\TfsWorkItemMigrationClient.cs:line 51
at VstsSyncMigrator.Engine.WorkItemMigrationContext.InternalExecute() in D:\a\1\s\src\VstsSyncMigrator.Core\Execution\MigrationContext\WorkItemMigrationContext.cs:line 117
at MigrationTools._EngineV1.Processors.MigrationProcessorBase.Execute() in D:\a\1\s\src\MigrationTools\_EngineV1\Processors\MigrationProcessorBase.cs:line 47
[07:54:31 ERR] WorkItemMigration The Processor MigrationEngine entered the failed state...stopping run
[07:54:31 INF] Application is shutting down...
[07:54:31 DBG] Hosting stopping
[07:54:31 DBG] Exiting with return code: 0
``
Of course source Area Path does not exist in Target project. How to resolve this?
Is there a way for the query to use one Area Path when executing in source and another Area path in Target.

The same query is run against both the Source and the Target. Therefor adding the NodePath to the query will result in an error if it does not also exist in the target (which it cant as the project name is in the path)
Use the NodePath filter argument instead.

Related

ReflectedWorkItemIDField Name for basic and scrum processes

Azure-devops-migrations-tools only works with custom processes , If we need to use the tool for existing (Basic, Scrum ,CMMI ) , What will be the Reflectedworkitemid Field name for the existing predefined processes in Azure devOps Services .
My requirement is to move work items from one project in one organization to another project different organization in Azure Devops Services.
I am stuck at the reflected workitemID ?
Attaching Logs
[10:47:34 ERR] Error running query
Microsoft.TeamFoundation.WorkItemTracking.Client.ValidationException: TF51005: The query references a field that does not exist. The error is caused by «[Scrum.ReflectedWorkItemId]».
at Microsoft.TeamFoundation.WorkItemTracking.Client.Query.Initialize(WorkItemStore store, String wiql, IDictionary context, Int32[] ids, Int32[] revs, Boolean dayPrecision)
at Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemStore.Query(String wiql, IDictionary context)
at MigrationTools._EngineV1.Clients.TfsWorkItemQuery.GetWorkItemsFromQuery(TfsWorkItemMigrationClient wiClient) in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.ObjectModel\_EngineV1\Clients\TfsWorkItemQuery.cs:line 40
[10:47:34 FTL] Error while running WorkItemMigration
Microsoft.TeamFoundation.WorkItemTracking.Client.ValidationException: TF51005: The query references a field that does not exist. The error is caused by «[Scrum.ReflectedWorkItemId]».
at Microsoft.TeamFoundation.WorkItemTracking.Client.Query.Initialize(WorkItemStore store, String wiql, IDictionary context, Int32[] ids, Int32[] revs, Boolean dayPrecision)
at Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemStore.Query(String wiql, IDictionary context)
at MigrationTools._EngineV1.Clients.TfsWorkItemQuery.GetWorkItemsFromQuery(TfsWorkItemMigrationClient wiClient) in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.ObjectModel\_EngineV1\Clients\TfsWorkItemQuery.cs:line 70
at MigrationTools._EngineV1.Clients.TfsWorkItemQuery.GetWorkItems() in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.ObjectModel\_EngineV1\Clients\TfsWorkItemQuery.cs:line 30
at MigrationTools._EngineV1.Clients.TfsWorkItemMigrationClient.FilterExistingWorkItems(List`1 sourceWorkItems, TfsWiqlDefinition wiqlDefinition, TfsWorkItemMigrationClient sourceWorkItemMigrationClient) in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.ObjectModel\_EngineV1\Clients\TfsWorkItemMigrationClient.cs:line 54
at VstsSyncMigrator.Engine.WorkItemMigrationContext.InternalExecute() in D:\a\1\s\src\VstsSyncMigrator.Core\Execution\MigrationContext\WorkItemMigrationContext.cs:line 120
at MigrationTools._EngineV1.Processors.MigrationProcessorBase.Execute() in D:\a\1\s\src\MigrationTools\_EngineV1\Processors\MigrationProcessorBase.cs:line 47
Technically, you could of course use an unused field from the original process templates (Scrum, ...) and then change the value accordingly in the configuration (e.g. integrated in build).
Why not just derive the process and add the field as described in the documentation? The inheritance process model actually makes this approach super easy. After migration, you can then simply switch your team project back to the model without the migration field.

Is it possible to use "Work items and direct link" type of query with Azure DevOps Migration tool

I'm trying to use the "azure-devops-migration-tool" to migrate Work items. What I'm trying to achieve is to query all items with closed not set and all the directly linked items with them in one query. This can be done in Azure DevOps UI, but I can't get the same query working in the tool.
An example query would be like this:
"QueryBit": "AND ( [Source].[System.WorkItemType] <> '' AND [Source].[System.State] <> '' AND [Source].[Microsoft.VSTS.Common.ClosedDate] = '') AND ([Target].[System.WorkItemType] <> '')"
Once running the tool I get an exception
[EXCEPTION] Microsoft.TeamFoundation.WorkItemTracking.Client.ValidationException: TF51005: The query references a field that does not exist. The error is caused by «Source.[System.WorkItemType]».
at Microsoft.TeamFoundation.WorkItemTracking.Client.Query.Initialize(WorkItemStore store, String wiql, IDictionary context, Int32[] ids, Int32[] revs, Boolean dayPrecision)
at Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemStore.Query(String wiql, IDictionary context)
at VstsSyncMigrator.Engine.TfsQueryContext.Execute() in d:\a\1\s\src\VstsSyncMigrator.Core\Execution\ComponentContext\TfsQueryContext.cs:line 72
migration.exe Warning: 0 : [EXCEPTION] Microsoft.TeamFoundation.WorkItemTracking.Client.ValidationException: TF51005: The query references a field that does not exist. The error is caused by «Source.[System.WorkItemType]».
at Microsoft.TeamFoundation.WorkItemTracking.Client.Query.Initialize(WorkItemStore store, String wiql, IDictionary context, Int32[] ids, Int32[] revs, Boolean dayPrecision)
at Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemStore.Query(String wiql, IDictionary context)
at VstsSyncMigrator.Engine.TfsQueryContext.Execute() in d:\a\1\s\src\VstsSyncMigrator.Core\Execution\ComponentContext\TfsQueryContext.cs:line 99
at VstsSyncMigrator.Engine.WorkItemMigrationContext.InternalExecute() in d:\a\1\s\src\VstsSyncMigrator.Core\Execution\MigrationContext\WorkItemMigrationContext.cs:line 101
at VstsSyncMigrator.Engine.MigrationContextBase.Execute() in d:\a\1\s\src\VstsSyncMigrator.Core\Execution\MigrationContext\MigrationContextBase.cs:line 35
Any suggestions?
Found the issue, and it was that the tool did not support to query from "WorkItemLinks".
It only supports "flat list of workitems type query"
try the wiql Editor plugin - https://marketplace.visualstudio.com/items?itemName=ottostreifel.wiql-editor
This lets you build queries with the UI and convert them to wiql with the editor. You can copy and paste them into your config file

Apache Ignite Query - No matching type found for object

I got "no matching type found for object" error when query cache keys from apache ignite cache.
Ignite server instance runs on Linux Server and my query runs on ignite client instance that started by Microsoft Server .Net Web Forms application. The dll for this type already exists in application's bin folder.
My Query:
List<string> cacheKeys = cache.Select(e => e.Key).Where(e => e.StartsWith(cacheItemKeyPrefix)).ToList();
Error :
Apache.Ignite.Core.Binary.BinaryObjectException: No matching type found for object [typeId=-274908056, typeName=System.Collections.Generic.Dictionary2[[System.Decimal],[CUST.CompositionTypes.PrivateBankingCustomer]]]. This usually indicates that assembly with specified type is not loaded on a node. When using Apache.Ignite.exe, make sure to load assemblies with -assembly parameter. Alternatively, set IgniteConfiguration.PeerAssemblyLoadingEnabled to true. at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type typeOverride) at Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type typeOverride) at Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride) at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadBinaryObject[T](Boolean doDetach) at Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type typeOverride) at Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride) at Apache.Ignite.Core.Impl.Cache.CacheEnumerator2.b__0(IBinaryStream stream) at Apache.Ignite.Core.Impl.PlatformJniTarget.OutStream[T](Int32 type, Func2 readAction) at Apache.Ignite.Core.Impl.Cache.CacheEnumeratorProxy2.MoveNext() at System.Linq.Enumerable.WhereSelectEnumerableIterator2.MoveNext() at System.Linq.Enumerable.WhereEnumerableIterator1.MoveNext() at System.Collections.Generic.List1..ctor(IEnumerable1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
You can only run .Net closures remotely if the whole cluster is .Net cluster, including server nodes. If they already are, I suggest some mismatch between windows and linux assemblies.
Do you have PrivateBankingCustomer type in your linux nodes' assemblies? Note that cache key/value types cannot be peer assembly loaded.

Infinispan Cache Indexing- org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper\write.lock

I am using Infinispan 8.2.2 in client-server mode (2 nodes 1 cluster), use replicated cache with indexing configuration as below. Data in getting indexed as well. I use a .proto file to map to my object and index some of the fields in the object as well. Whenever I writes to cache for each row write, below exception occurs. Could you please help.
Configuration
`<replicated-cache name="tickets-cache" mode="ASYNC" start="EAGER">
<indexing index="ALL">
property name="default.indexmanager">near-real-time</property
<property name="lucene_version">LUCENE_CURRENT</property>
<property name="default.chunk_size">128000</property>
</indexing>
<locking acquire-timeout="60000"/>
<expiration lifespan="43200000"/>
</replicated-cache>`
Exception
Exception
2016-08-04 20:59:08,318 ERROR [org.hibernate.search.exception.impl.LogErrorHandler] (Hibernate Search sync consumer thread for index org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper) HSEARCH000058: Exception occurred org.apache.lucene.store.LockObtainFailedException: Lock held by another program: D:\WorkSpace\Softwares\infinispan-server-8.2.2.Final\org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper\write.lock
Primary Failure:
Entity org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper Id A:SgRCQUcx Work Type org.hibernate.search.backend.UpdateLuceneWork
: org.apache.lucene.store.LockObtainFailedException: Lock held by another program: D:\WorkSpace\Softwares\infinispan-server-8.2.2.Final\org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper\write.lock
at org.apache.lucene.store.NativeFSLockFactory.obtainFSLock(NativeFSLockFactory.java:118)
at org.apache.lucene.store.FSLockFactory.obtainLock(FSLockFactory.java:41)
at org.apache.lucene.store.BaseDirectory.obtainLock(BaseDirectory.java:45)
at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:776)
at org.hibernate.search.backend.impl.lucene.IndexWriterHolder.createNewIndexWriter(IndexWriterHolder.java:123)
at org.hibernate.search.backend.impl.lucene.IndexWriterHolder.getIndexWriter(IndexWriterHolder.java:89)
at org.hibernate.search.backend.impl.lucene.AbstractWorkspaceImpl.getIndexWriter(AbstractWorkspaceImpl.java:117)
at org.hibernate.search.backend.impl.lucene.AbstractWorkspaceImpl.getIndexWriterDelegate(AbstractWorkspaceImpl.java:203)
at org.hibernate.search.backend.impl.lucene.LuceneBackendQueueTask.applyUpdates(LuceneBackendQueueTask.java:80)
at org.hibernate.search.backend.impl.lucene.LuceneBackendQueueTask.run(LuceneBackendQueueTask.java:46)
at org.hibernate.search.backend.impl.lucene.SyncWorkProcessor$Consumer.applyChangesets(SyncWorkProcessor.java:162)
at org.hibernate.search.backend.impl.lucene.SyncWorkProcessor$Consumer.run(SyncWorkProcessor.java:148)
at java.lang.Thread.run(Thread.java:745)
2016-08-04 20:59:08,320 ERROR [org.hibernate.search.backend.impl.lucene.LuceneBackendQueueTask] (Hibernate Search sync consumer thread for index org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper) HSEARCH000072: Couldn't open the IndexWriter because of previous error: operation skipped, index ouf of sync!
2016-08-04 20:59:55,255 INFO [org.jboss.as.clustering.infinispan] (remote-thread--p2-t13) DGISPN0001: Started ___event_log_cache cache from clustered container
2016-08-04 20:59:55,403 INFO [org.jboss.as.clustering.infinispan] (remote-thread--p2-t13) DGISPN0001: Started ___query_cache cache from clustered container
2016-08-04 21:00:12,036 ERROR [org.hibernate.search.exception.impl.LogErrorHandler] (Hibernate Search sync consumer thread for index org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper) HSEARCH000058: Exception occurred org.apache.lucene.store.LockObtainFailedException: Lock held by another program: D:\WorkSpace\Softwares\infinispan-server-8.2.2.Final\org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper\write.lock
Primary Failure:
Entity org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper Id A:SgRCQUcw Work Type org.hibernate.search.backend.UpdateLuceneWork
: org.apache.lucene.store.LockObtainFailedException: Lock held by another program: D:\WorkSpace\Softwares\infinispan-server-8.2.2.Final\org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper\write.lock
at org.apache.lucene.store.NativeFSLockFactory.obtainFSLock(NativeFSLockFactory.java:118)
at org.apache.lucene.store.FSLockFactory.obtainLock(FSLockFactory.java:41)
at org.apache.lucene.store.BaseDirectory.obtainLock(BaseDirectory.java:45)
at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:776)
at org.hibernate.search.backend.impl.lucene.IndexWriterHolder.createNewIndexWriter(IndexWriterHolder.java:123)
at org.hibernate.search.backend.impl.lucene.IndexWriterHolder.getIndexWriter(IndexWriterHolder.java:89)
at org.hibernate.search.backend.impl.lucene.AbstractWorkspaceImpl.getIndexWriter(AbstractWorkspaceImpl.java:117)
at org.hibernate.search.backend.impl.lucene.AbstractWorkspaceImpl.getIndexWriterDelegate(AbstractWorkspaceImpl.java:203)
at org.hibernate.search.backend.impl.lucene.LuceneBackendQueueTask.applyUpdates(LuceneBackendQueueTask.java:80)
at org.hibernate.search.backend.impl.lucene.LuceneBackendQueueTask.run(LuceneBackendQueueTask.java:46)
at org.hibernate.search.backend.impl.lucene.SyncWorkProcessor$Consumer.applyChangesets(SyncWorkProcessor.java:162)
at org.hibernate.search.backend.impl.lucene.SyncWorkProcessor$Consumer.run(SyncWorkProcessor.java:148)
at java.lang.Thread.run(Thread.java:745)

Broken Publish in VB.net

I have managed to break my Project>Publish ability in a vb.net project. I wanted to include some files with the installer and tried doing this using Project>Properties>Resources>Files and Add Resource. That failed so I went back there and removed the resources. I can publish the project but when I try to run the setup.exe it gives a 'contact the vendor error' and looking at the log has an error like below. I'm stuck.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* An exception occurred while determining trust. Following failure messages were detected:
+ Value does not fall within the expected range.
Activation of C:\Documents and Settings\Bob&Sue\My Documents\Visual Studio 2010\Projects\Spiffy\Spiffy\publish\Spiffy.application resulted in exception. Following failure messages were detected:
+ Value does not fall within the expected range.
I created a new project (Junk28APR12) which just has Form1 and Label1 (with text 'Hello World!') and that will publish but again I can't successfully run the setup.exe. Here is the full error log from that:
PLATFORM VERSION INFO
Windows : 5.1.2600.196608 (Win32NT)
Common Language Runtime : 4.0.30319.239
System.Deployment.dll : 4.0.30319.1 (RTMRel.030319-0100)
clr.dll : 4.0.30319.239 (RTMGDR.030319-2300)
dfdll.dll : 4.0.30319.1 (RTMRel.030319-0100)
dfshim.dll : 4.0.31106.0 (Main.031106-0000)
SOURCES
Deployment url : file:///C:/Documents%20and%20Settings/Bob&Sue/My%20Documents/Visual%20Studio%202010/Projects/Junk28APR12/Junk28APR12/publish/Junk28APR12.application
Application url : file:///C:/Documents%20and%20Settings/Bob&Sue/My%20Documents/Visual%20Studio%202010/Projects/Junk28APR12/Junk28APR12/publish/Application%20Files/Junk28APR12_1_0_0_0/Junk28APR12.exe.manifest
IDENTITIES
Deployment Identity : Junk28APR12.application, Version=1.0.0.0, Culture=neutral, PublicKeyToken=18093298bace470a, processorArchitecture=x86
Application Identity : Junk28APR12.exe, Version=1.0.0.0, Culture=neutral, PublicKeyToken=18093298bace470a, processorArchitecture=x86, type=win32
APPLICATION SUMMARY
* Installable application.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* An exception occurred while determining trust. Following failure messages were detected:
+ Value does not fall within the expected range.
* Activation of C:\Documents and Settings\Bob&Sue\My Documents\Visual Studio 2010\Projects\Junk28APR12\Junk28APR12\publish\Junk28APR12.application resulted in exception. Following failure messages were detected:
+ Value does not fall within the expected range.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [28/04/2012 11:12:14] : Activation of C:\Documents and Settings\Bob&Sue\My Documents\Visual Studio 2010\Projects\Junk28APR12\Junk28APR12\publish\Junk28APR12.application has started.
* [28/04/2012 11:12:14] : Processing of deployment manifest has successfully completed.
* [28/04/2012 11:12:14] : Installation of the application has started.
* [28/04/2012 11:12:14] : Processing of application manifest has successfully completed.
* [28/04/2012 11:12:15] : Found compatible runtime version 4.0.30319.
ERROR DETAILS
Following errors were detected during this operation.
* [28/04/2012 11:12:15] System.ArgumentException
- Value does not fall within the expected range.
- Source: mscorlib
- Stack trace:
at System.Deployment.Internal.Isolation.IDefinitionAppId.EnumAppPath()
at System.ActivationContext.CreateFromNameAndManifests(ApplicationIdentity applicationIdentity, String[] manifestPaths)
at System.Deployment.Application.ActivationDescription.ToActivationContext()
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
* [28/04/2012 11:12:15] System.ArgumentException
- Value does not fall within the expected range.
- Source: mscorlib
- Stack trace:
at System.Deployment.Internal.Isolation.IDefinitionAppId.EnumAppPath()
at System.ActivationContext.CreateFromNameAndManifests(ApplicationIdentity applicationIdentity, String[] manifestPaths)
at System.Deployment.Application.ActivationDescription.ToActivationContext()
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
Thanks Jim, your link prompted the solution. It is because I have an '&' in my user name, so the default publish path has an '&' in it which causes the issue. I simply changed the publish path to be outside of My Documents and it worked.
I have created a Folder C:\VB_NET\ and in future things will go in there (certainly publishes and maybe future projects too).
MS know this issue and aren't going to fix it apparently. I'm fine with that, but they should make it more obvious that that is what the problem is.