This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
My viusal studio crashed on my while compiling a SCSS and now anytime I hit save on any SCSS it has this output:
Exception Type: System.NullReferenceException
Exception Message: Object reference not set to an instance of an object.
Exception Stack Trace: at DPStudio.VSCommands.Features.Text.Tagging.Tagger.AfterDocumentSaved(DocumentEventArgs e)
at Microsoft.Practices.Prism.Events.EventSubscription`1.InvokeAction(Action`1 action, TPayload argument)
at Microsoft.Practices.Prism.Events.EventSubscription`1.<>c__DisplayClass2.<GetExecutionStrategy>b__0(Object[] arguments)
at Microsoft.Practices.Prism.Events.EventBase.InternalPublish(Object[] arguments)
at Microsoft.Practices.Prism.Events.CompositePresentationEvent`1.Publish(TPayload payload)
at DPStudio.VSCommands.Foundation.Services.VisualStudioEventsListenerService.DocumentEvents_DocumentSaved(Document Documen
Hope this means something to you.
|
|
|
|
|
Hmm, that crash is happening instead VSCommands 2010 (http://visualstudiogallery.msdn.microsoft.com/d491911d-97f3-4cf6-87b0-6a2882120acf), not inside Web Workbench. It may be that he's trying to do something with the generated CSS document, which may be null because it was not regenerated properly after the earlier Visual Studio crash. Without knowing the internals of VSCommands I'm not sure how to resolve this but I would suggest temporarily removing the SCSS file from your project, saving the project, restarting Visual Studio and then adding the SCSS file back into the project. I also wonder if this: http://getsatisfaction.com/dpstudio/topics/errors_when_creating_and_saving_file_that_has_unknown_file_extension from the VSCommands support forum might be relevant. The exception type and stack trace look identical. |
|
|
|
