locked
problem after VS 2012 update

    General discussion

  •  

    Hello!

    I've just download an update to Visual Studio 2012.

    After that I'm getting a problem with XAML pages that are located in class library (this problem doesn't occure in V2 2012 without update).

    Every time I'm trying to lauch this kind of page I'm getting "XAML parsing failed.".

    This problem is not connected with dots in library name (there was a hotfix for this problem).

    Any ideas?

    Thanks in advance for any help.

     

    Wednesday, November 28, 2012 12:54 PM

All replies

  • We would love to take a look, but will need a repro project.

    Could you please get in touch with me directly at unnir at Microsoft dot com with the project repro so we can investigate?

    Thanks,

    Unni


    Unni Ravindranathan, Program Manager, Visual Studio and Blend This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, November 29, 2012 6:53 AM
  • I have a same problem when I finished my updating process, I cannot open XAML.

    The following are the error code I get.

    System.Exception
    
    Package could not be registered. (Exception from HRESULT: 0x80073CF3)
    
       at Microsoft.Expression.HostUtility.Platform.AppContainerProcessDomainFactory.CreateDesignerProcess(String applicationPath, String clientPort, Uri hostUri, IDictionary environmentVariables, Int32& processId, Object& processData)
       at Microsoft.Expression.DesignHost.Isolation.Primitives.ProcessDomainFactory.ProcessIsolationDomain..ctor(ProcessDomainFactory factory, IIsolationBoundary boundary, AppDomainSetup appDomainInfo, FrameworkName targetFramework, String identifier, String baseDirectory)
       at Microsoft.Expression.DesignHost.Isolation.Primitives.ProcessDomainFactory.CreateIsolationDomain(IIsolationBoundary boundary)
       at Microsoft.Expression.HostUtility.Platform.AppContainerProcessDomainFactory.CreateIsolationDomain(IIsolationBoundary boundary)
       at Microsoft.Expression.DesignHost.Isolation.Primitives.IsolationBoundary.Initialize()
       at Microsoft.Expression.DesignHost.Isolation.Primitives.IsolationBoundary.CreateInstance[T](Type type)
       at Microsoft.Expression.DesignHost.Isolation.IsolatedExportProvider.Initialize()
       at Microsoft.VisualStudio.ExpressionHost.Services.VSIsolationService.CreateExportProvider(IIsolationTarget isolationTarget, ICatalogFactory catalogFactory, IExportFilter filter)
       at Microsoft.Expression.DesignHost.Isolation.IsolationService.CreateLease(IIsolationTarget isolationTarget)
       at Microsoft.Expression.DesignHost.IsolatedDesignerService.CreateLease(IIsolationTarget isolationTarget, CancellationToken cancelToken, DesignerServiceEntry& entry)
       at Microsoft.Expression.DesignHost.IsolatedDesignerService.IsolatedDesignerView.CreateDesignerViewInfo(CancellationToken cancelToken)
       at Microsoft.Expression.DesignHost.Isolation.IsolatedTaskScheduler.InvokeWithCulture[T](CultureInfo culture, Func`2 func, CancellationToken cancelToken)
       at Microsoft.Expression.DesignHost.Isolation.IsolatedTaskScheduler.<>c__DisplayClassa`1.<StartTask>b__6()
       at System.Threading.Tasks.Task`1.InnerInvoke()
       at System.Threading.Tasks.Task.Execute()

    Could you please tell me how to fix this problem?

    Thanks~~~

    Thursday, November 29, 2012 8:34 AM
  • I too am having the same problem after the VS update. Unfortunately, my application is rather too large and proprietary to be uploaded as an example for Microsoft to play with :(.
    (P.S. I do not have dots/periods in my assembly names (that triggered a similar bug in some previous version of VS2012).
    • Edited by squizfloats Saturday, December 01, 2012 5:53 PM more info
    Saturday, December 01, 2012 5:49 PM
  • There is a workaround for this problem. Just try to set assembly name the same as default namespace. That should work. If not please contact me direclty on email w.zubik at jojomobile dot pl.

    Monday, December 03, 2012 7:50 AM