Thread overview
Can someone please tell me what is wrong with my Visual D.
Dec 11, 2013
Siavash Babaei
Dec 11, 2013
Siavash Babaei
Dec 13, 2013
Rainer Schuetze
Dec 15, 2013
Siavash Babaei
December 11, 2013
I have the latest compiler and Visual D + Visual Studio 2013 Ultimate + Win7x64. BTW, This is happening on 2 PCs and 3 Laptops!

Error occurred while restoring NuGet packages:
System.ComponentModel.Composition.CompositionException: The
composition produced a single composition error. The root cause
is provided below. Review the CompositionException.Errors
property for more detailed information.

1) The method or operation is not implemented.

Resulting in: An exception occurred while trying to create an
instance of type 'NuGet.VisualStudio.SolutionManager'.

Resulting in: Cannot activate part
'NuGet.VisualStudio.SolutionManager'.
Element: NuGet.VisualStudio.SolutionManager -->
NuGet.VisualStudio.SolutionManager

Resulting in: Cannot get export
'NuGet.VisualStudio.SolutionManager
(ContractName="NuGet.VisualStudio.ISolutionManager")' from part
'NuGet.VisualStudio.SolutionManager'.
Element: NuGet.VisualStudio.SolutionManager
(ContractName="NuGet.VisualStudio.ISolutionManager") -->
NuGet.VisualStudio.SolutionManager

Resulting in: Cannot set import
'NuGet.VisualStudio.VsSettings..ctor
(Parameter="solutionManager",
ContractName="NuGet.VisualStudio.ISolutionManager")' on part
'NuGet.VisualStudio.VsSettings'.
Element: NuGet.VisualStudio.VsSettings..ctor
(Parameter="solutionManager",
ContractName="NuGet.VisualStudio.ISolutionManager") -->
NuGet.VisualStudio.VsSettings

Resulting in: Cannot get export 'NuGet.VisualStudio.VsSettings
(ContractName="NuGet.ISettings")' from part
'NuGet.VisualStudio.VsSettings'.
Element: NuGet.VisualStudio.VsSettings
(ContractName="NuGet.ISettings") -->
NuGet.VisualStudio.VsSettings

   at
System.ComponentModel.Composition.Hosting.CompositionServices.GetExportedValueFromComposedPart(ImportEngine
engine, ComposablePart part, ExportDefinition definition)
   at
System.ComponentModel.Composition.Hosting.CatalogExportProvider.GetExportedValue(CatalogPart
part, ExportDefinition export, Boolean isSharedPart)
   at
System.ComponentModel.Composition.Hosting.CatalogExportProvider.CatalogExport.GetExportedValueCore()
   at
System.ComponentModel.Composition.Primitives.Export.get_Value()
   at
System.ComponentModel.Composition.ExportServices.GetCastedExportedValue[T](Export
export)
   at
System.ComponentModel.Composition.Hosting.ExportProvider.GetExportedValueCore[T](String
contractName, ImportCardinality cardinality)
   at
System.ComponentModel.Composition.Hosting.ExportProvider.GetExportedValue[T](String
contractName)
   at
System.ComponentModel.Composition.Hosting.ExportProvider.GetExportedValue[T]()
   at
Microsoft.VisualStudio.ComponentModelHost.ComponentModel.GetService[T]()
   at
NuGet.VisualStudio.ServiceLocator.GetComponentModelService[TService]()
   at NuGet.VisualStudio.ServiceLocator.GetInstance[TService]()
   at NuGet.VsEvents.PackageRestorer.IsAutomatic()
   at
NuGet.VsEvents.PackageRestorer.BuildEvents_OnBuildBegin(vsBuildScope
Scope, vsBuildAction Action).
------ Build started: Project: Hello, Configuration: Debug DMD
Win32 ------
Building Debug DMD Win32\Hello.exe...
Converting debug information...
D:\SkyDrive\Documents\Visual Studio
2013\Projects\D\Studies\Hello\Hello\Debug DMD Win32\Hello.pdb:
cannot add symbols to module, probably msobj80.dll missing
Building Debug DMD Win32\Hello.exe failed!
Details saved as "file://D:\SkyDrive\Documents\Visual Studio
2013\Projects\D\Studies\Hello\Hello\Debug DMD
Win32\Hello.buildlog.html"
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped
==========

Command Line

set PATH=D:\DLang\dmd2\windows\\bin;C:\Program Files
(x86)\Microsoft SDKs\Windows\v7.0A\\\bin;%PATH%
dmd -g -debug -X -Xf"Debug DMD Win32\Hello.json" -deps="Debug DMD
Win32\Hello.dep" -c -of"Debug DMD Win32\Hello.obj" main.d
if errorlevel 1 goto reportError

set LIB="D:\DLang\dmd2\windows\bin\..\lib"
echo. >
D:\SkyDrive\DOCUME~1\VISUAL~3\Projects\D\Studies\Hello\Hello\DEBUGD~1\HELLOB~1.LNK
echo "Debug DMD Win32\Hello.obj","Debug DMD
Win32\Hello.exe_cv","Debug DMD Win32\Hello.map",user32.lib+ >>
D:\SkyDrive\DOCUME~1\VISUAL~3\Projects\D\Studies\Hello\Hello\DEBUGD~1\HELLOB~1.LNK
echo kernel32.lib/NOMAP/CO/NOI >>
D:\SkyDrive\DOCUME~1\VISUAL~3\Projects\D\Studies\Hello\Hello\DEBUGD~1\HELLOB~1.LNK

"d:\Program Files (x86)\VisualD\pipedmd.exe" -deps "Debug DMD
Win32\Hello.lnkdep" D:\DLang\dmd2\windows\bin\link.exe
@D:\SkyDrive\DOCUME~1\VISUAL~3\Projects\D\Studies\Hello\Hello\DEBUGD~1\HELLOB~1.LNK
if errorlevel 1 goto reportError
if not exist "Debug DMD Win32\Hello.exe_cv" (echo "Debug DMD
Win32\Hello.exe_cv" not created! && goto reportError)
echo Converting debug information...
"d:\Program Files (x86)\VisualD\cv2pdb\cv2pdb.exe" "Debug DMD
Win32\Hello.exe_cv" "Debug DMD Win32\Hello.exe"
if errorlevel 1 goto reportError
if not exist "Debug DMD Win32\Hello.exe" (echo "Debug DMD
Win32\Hello.exe" not created! && goto reportError)

goto noError

:reportError
echo Building Debug DMD Win32\Hello.exe failed!

:noError
Output

Converting debug information...
D:\SkyDrive\Documents\Visual Studio
2013\Projects\D\Studies\Hello\Hello\Debug DMD Win32\Hello.pdb:
cannot add symbols to module, probably msobj80.dll missing
Building Debug DMD Win32\Hello.exe failed!
December 11, 2013
Ah, installing "VisualD-v0.3.38-beta1b" seems to have fixed the problem for the moment. In time, maybe a dedicated IDE that can give maximum comfort and functionality may not be such a bad idea! Hope DM gets to that sometime ...
December 13, 2013

On 11.12.2013 16:46, Siavash Babaei wrote:
> Ah, installing "VisualD-v0.3.38-beta1b" seems to have fixed the problem
> for the moment. In time, maybe a dedicated IDE that can give maximum
> comfort and functionality may not be such a bad idea! Hope DM gets to
> that sometime ...

There were some fixes for finding the correct mspdb*.dll when multiple versions of Visual Studio are installed. Good to hear it worked for you.

I have no clue what the NuGet messages mean, I guess they are not related to Visual D.
December 15, 2013
Thank you for the fix and the brilliant add-on to VS.