Install Visual Studio 2015 express on Windows 7 - visual-studio

I have read this, this, this, this and this questions and answers, none of them have help me at all.
I'm trying to install Visual Studio 2015 Express or Community edition, I have W7 SP1, I have tried with admin rights, I've checked that no preview VS have been installed but no matter what I do, I still can't install VS and I don't understand what the log says, I'll append a picture and what I think is an important part of the log file:
[0D48:1794][2015-10-20T19:36:45]i000: MUX: Feed uri to register: http://go.microsoft.com/fwlink/?LinkID=558779&clcid=0x409
[0D48:1794][2015-10-20T19:36:47]e000: MUX: Exception: Info: Unable to load dynamic feed
[0D48:1794][2015-10-20T19:36:47]e000: MUX: ERROR: Could not load file or assembly 'System.Security, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The module was expected to contain an assembly manifest.
[0D48:1794][2015-10-20T19:36:47]e000: MUX: Stack: at Microsoft.Web.PlatformInstaller.Util.IsSignatureValid(String xmlFile)
at Microsoft.Web.PlatformInstaller.ProductManager.LoadFromXml(String xmlFile, Boolean loadEnclosures, Boolean isOnlineFeedLoaded, Boolean verifySignature)
at Microsoft.Web.PlatformInstaller.ProductManager.Load(Uri productFileUrl, Boolean filterByArchitectureAndOS, Boolean loadEnclosures, Boolean useCachedVersion, String cacheDirectory, Architecture architecture, Int32 osType, String& finalFeedCacheLocation, Boolean& isOnlineFeedLoaded, Boolean& onlineFeedLoadError, String localFeed, Boolean verifySignature, String feedUri, String lastUsedFeedLocationKey, BundleProperties currentBundle)
at Microsoft.Web.PlatformInstaller.ProductManager.Load(Uri productFileUrl, Boolean filterByArchitectureAndOS, Boolean loadEnclosures, Boolean useCachedVersion, String cacheDirectory, String& finalFeedCacheLocation, Boolean& isOnlineFeedLoaded, Boolean& onlineFeedLoadError, String localFeed, Boolean verifySignature, String feedUri, String lastUsedFeedLocationKey, BundleProperties currentBundle)
at Microsoft.Devdiv.Bootstrapper.Utility.SecondaryInstallerUtility.LoadProductManager()
[0D48:05C8][2015-10-20T19:36:54]i000: MUX: View loaded
[0D48:05C8][2015-10-20T19:36:54]i000: MUX: Go to Blocker page.
[0D48:05C8][2015-10-20T19:36:54]i199: Detect complete, result: 0x0
Apparently, the problem is in:
Could not load file or assembly
'System.Security, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a'
UPDATE
After devlin carnate suggestion and reading answers from this site and this one too I have tried the following:
Update my OS. Except for the "update to W10" I have installed all updates (even some of those marked as optionals).
Run a "scan now" from command prompt, bassically, I followed instructions from this site, and even when something were marked as corrupted I don't know how to repair it ('cause no dll or file were detected).
Uninstall the .NET Framework and install a prev version (from 4.5 to 4) but the problem persist (also, after this, windows suggest to update to 4.5 so I reinstall 4.5 version).
Use the .NET Framework Repair Tool with no results.
UPDATE 2
I just format my HDD unit and reinstall (the same) W7 SP1 all over again, after that, I was able to install VS Community Edition, but I don't take this as a solution since is just too drastic and I don't know the original reason of why this happened in the first place.

Related

Xamarin Studio for Mac throwing exceptions in FSI - `seems` not to be loading core F# libs

Sorry for all the long error messages! I wonder if there is something wrong with my Xamarin, or Mono install which is breaking FSI on Xamarin? Default .Net runtime is Mono 4.6.2 Although I have installed Mono 4.8.0, Xamarin is running on 4.6.2
I wonder if these error messages mean that FSI isn't loading the System.Drawing module? And why is SOURCE_DIRECTORY seemingly not working? There are no errors displayed in the .fsx file but when loaded into FSI it doesn't work.
I've also got Visual Studio for Mac installed. I'm just starting with F# (day 3) and this is the first time I've tried to open a System module so I've not idea if it ever worked. Basic functions I write myself will evaluate in FSI. I'm considering the possibility that the install has been screwed up somewhere and am wondering if I should just remove .Net, Xamarin and Mono and reinstall from scratch? Is it possible for Visual Studio to interfere with Xamarin?
Going through the FSharp TV intro course I'm running the following errors
F# in a .fsx file:
open System.Drawing
let bitmap = new Bitmap(32,32)
let path = __SOURCE_DIRECTORY__ + "/"
bitmap.Save (path + "large.png")
Loading the entire code block in FSI throws:
System.Exception: Generic Error [GDI+ status: GenericError]
  at System.Drawing.GDIPlus.CheckStatus (System.Drawing.Status status) [0x0007a] in <1917aa1c39d94b1a91807b8cd9f03350>:0
  at System.Drawing.Image.Save (System.String filename, System.Drawing.Imaging.ImageCodecInfo encoder, System.Drawing.Imaging.EncoderParameters encoderParams) [0x00043] in <1917aa1c39d94b1a91807b8cd9f03350>:0
  at System.Drawing.Image.Save (System.String filename, System.Drawing.Imaging.ImageFormat format) [0x0004c] in <1917aa1c39d94b1a91807b8cd9f03350>:0
  at System.Drawing.Image.Save (System.String filename) [0x00008] in <1917aa1c39d94b1a91807b8cd9f03350>:0
  at (wrapper remoting-invoke-with-check) System.Drawing.Image:Save (string)
  at <StartupCode$FSI_0004>.$FSI_0004.main# () [0x0003d] in <2545683d6122431b9ff3a69ce9ec460c>:0
  at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&)
  at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00038] in <8f2c484307284b51944a1a13a14c0266>:0
Loading only SOURCE_DIRECTORY in FSI returns:
val it : string = "/"
which is weird because that's not the correct path
Loading the line: let bitmap = new Bitmap(32,32)
throws:
Stopped due to error
 System.Exception: Operation could not be completed due to earlier error
 The type 'Bitmap' is not defined at 2,4
Sending System.Drawing to FSI
throws:
Stopped due to error
 System.Exception: Operation could not be completed due to earlier error
 The value, constructor, namespace or type 'Drawing' is not defined at 2,7
It looks like you might be hitting a Mono bug. I've found several reports of what looks like the same bug (though it's possible that it's several different bugs). The most useful one appears to be this Github issue: https://github.com/gitextensions/gitextensions/issues/2226
I don't know if that will help you; that issue appears to have been resolved by upgrading from Mono 3.2.8 to the latest version of Mono available at the time. But you're already running what appears to be the latest version of Mono available to you, so "upgrade to the latest Mono" may not be the advice for your problem. But it's the best advice I'm able to give.
Also, in doing that search, I found several people complaining that libgdiplus (Mono's implementation of the GDIPlus API) was buggy in various ways. So in your shoes, I might skip the System.Drawing examples and move on to a different part of the tutorial if you can't get libgdiplus to work.
P.S. The below is what I first wrote in answer to your question, but then I experimented and discovered that the System.Drawing namespace is automatically loaded in F# scripts without you needing to explicitly open it. Still, as an F# beginner, you may find the information below to be useful in other contexts, so I've left it in. Just be aware that what I said below about System.Drawing not being automatically opened was wrong.
----- Not-quite-correct answer follows -----
When writing an F# script in a .fsx file, you can't just do open (namespace). You also have to tell F# where to find the .DLL with that namespace. In a compiled project (which uses .fs files), that information would be found in the .fsproj file. But for F# scripts (the .fsx format), there's no project file, so the script itself needs to specify which DLLs to load. You do this by the #r directive:
#r "/path/to/library.dll"
Or, if the DLL you're loading is installed in a standard system location such as the GAC (Global Assembly Cache), you can leave off the path and just do:
#r "library.dll"
There are a few DLLs that are automatically loaded whenever you run an F# script, such as mscorlib.dll that contains things like the System namespace. But the System.Drawing namespace is not one of those automatically-loaded DLLs. So before you can open the System.Drawing namespace, you have to put in the appropriate #r reference, like so:
#r "System.Drawing.dll"
open System.Drawing

Visual Studio Code Cannot Configure Correctly

For some reason, most likely because I do not know how to configure Visual Studio Code. We are talking about the free light version.
It is always showing an error of some type. I am new to this product, NOT VS but this version of it.
How do we set this IDE up correct to work with it?
Here is my current error.
Downloading and configuring the .NET Core Debugger...
Telemetry is: Enabled
log : Restoring packages for C:\Users\Erik Little\.vscode\extensions\ms-vscode.csharp-0.3.7\coreclr-debug\project.json...
info : Committing restore...
log : Lock file has not changed. Skipping lock file write. Path: C:\Users\Erik Little\.vscode\extensions\ms-vscode.csharp-0.3.7\coreclr-debug\project.lock.json
log : C:\Users\Erik Little\.vscode\extensions\ms-vscode.csharp-0.3.7\coreclr-debug\project.json
log : Restore completed in 585ms.
NuGet Config files used:
C:\Users\Erik Little\.vscode\extensions\ms-vscode.csharp-0.3.7\coreclr-debug\NuGet.config
Feeds used:
https://www.myget.org/F/dotnet-core/api/v3/index.json
https://api.nuget.org/v3/index.json
https://www.myget.org/F/coreclr-debug/api/v3/index.json
Telemetry is: Enabled
Error: Can not find runtime target for framework 'DNXCore,Version=v5.0' compatible with one of the target runtimes: 'win10-x64, win81-x64, win8-x64, win7-x64'. Possible causes:
1. The project has not been restored or restore failed - run `dotnet restore`
2. The project does not list one of 'win10-x64, win81-x64, win8-x64, win7-x64' in the 'runtimes' section.
Error:
System.InvalidOperationException: Can not find runtime target for framework 'DNXCore,Version=v5.0' compatible with one of the target runtimes: 'win10-x64, win81-x64, win8-x64, win7-x64'. Possible causes:
1. The project has not been restored or restore failed - run `dotnet restore`
2. The project does not list one of 'win10-x64, win81-x64, win8-x64, win7-x64' in the 'runtimes' section.
at Microsoft.DotNet.ProjectModel.BuildWorkspace.GetRuntimeContext(ProjectContext context, IEnumerable`1 runtimeIdentifiers)
at Microsoft.DotNet.Tools.Publish.PublishCommand.<>c__DisplayClass71_0.<SelectContexts>b__1(ProjectContext c)
at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at Microsoft.DotNet.Tools.Publish.PublishCommand.TryPrepareForPublish()
at Microsoft.DotNet.Tools.Publish.PublishCommand.<>c__DisplayClass0_0.<Run>b__0()
at Microsoft.DotNet.Cli.CommandLine.CommandLineApplication.Execute(String[] args)
at Microsoft.DotNet.Tools.Publish.PublishCommand.Run(String[] args)
dotnet exited with error code 1
Error while installing .NET Core Debugger.
They make it seem so easy to set up but there is always something that i am missing. I have a very good thought that I am not setting up the configuration file correctly because it looks strange to me. Looks like all JS.
Also if I point to a folder that I work in with no issues at all with visual studio enterprise edition I always get this error
eslintrc-error
It keeps looking for eslintrc but i have looked everywhere to resolve this.
I've posted a snapshot of this issue as well.
I know is must be a config issue.
I do not even know what eslintrc is.
Please advise.
It's a linter for ecma... the rc file configures its options.
So you're aware code is an editor, not really an IDE. If you're looking for free I'd suggest Visual Studio Community.

Xamarin iOS - Could not load file or assembly 'System.Threading.Tasks' at startup

I just upgraded to Xamarin studio 5.9 (build 431), and cannot run my project anymore. It works with a clean project though.
When I run my app, I don't even land in Main.
The Application Output in Xamarin studio prints a bunch of assembly loadings. It gets to MobileClientiOS.app/Newtonsoft.Json.dll [External], then it crashes with the following output:
Could not load file or assembly 'System.Threading.Tasks' or one of its
dependencies. The system cannot find the file specified.
(System.IO.FileNotFoundException) at System.AppDomain.Load
(System.Reflection.AssemblyName assemblyRef,
System.Security.Policy.Evidence assemblySecurity) [0x00081] in
.../mono/mcs/class/corlib/System/AppDomain.cs:706 at
System.AppDomain.Load (System.Reflection.AssemblyName assemblyRef)
[0x00000] in .../mono/mcs/class/corlib/System/AppDomain.cs:674 at
System.Reflection.Assembly.Load (System.Reflection.AssemblyName
assemblyRef) [0x00000] in
.../mono/mcs/class/corlib/System.Reflection/Assembly.cs:551 at
ObjCRuntime.Runtime.CollectReferencedAssemblies
(System.Collections.Generic.List 1 assemblies,
System.Reflection.Assembly assembly) [0x00019] in
.../maccore/src/ObjCRuntime/Runtime.cs:218 at
ObjCRuntime.Runtime.CollectReferencedAssemblies
(System.Collections.Generic.List 1 assemblies,
System.Reflection.Assembly assembly) [0x0002c] in
.../maccore/src/ObjCRuntime/Runtime.cs:220 at
ObjCRuntime.Runtime.CollectReferencedAssemblies
(System.Collections.Generic.List 1 assemblies,
System.Reflection.Assembly assembly) [0x0002c] in
.../maccore/src/ObjCRuntime/Runtime.cs:220 at
ObjCRuntime.Runtime.RegisterEntryAssembly (System.Reflection.Assembly
entry_assembly) [0x0001b] in
.../maccore/src/ObjCRuntime/Runtime.cs:200 at
ObjCRuntime.Runtime.RegisterEntryAssembly (IntPtr a) [0x00000] in
.../maccore/src/ObjCRuntime/Runtime.cs:158 at
ObjCRuntime.Runtime.register_entry_assembly (IntPtr assembly)
[0x00000] in .../maccore/runtime/Delegates.generated.cs:118 at
(wrapper native-to-managed)
ObjCRuntime.Runtime:register_entry_assembly (intptr) 2015-05-04
MobileClientiOS[77830:1943120] critical: Got a SIGABRT while
executing native code. This usually indicates a fatal error in the
mono runtime or one of the native libraries used by your application.
Sorry for the long stacktrace, but I'm out of ideas. We are using PCL's, but there haven't been a problem before this Xamarin Studio-upgrade.
Thank you!
Edit:
I downgraded Xamarin.iOS and it's working again. The assembly it seems to fail on is (which now works with the old version):
/MobileClientiOS.app/System.Xml.Linq.dll [External]
How to be able to run with the latest version? I do not know.
To make a guess, I think this might have the same underlying cause as Xamarin Bug 29211.
If that's true, then there's a good chance the same workaround will work:
Under "project options -> iOS Build -> Additional mtouch arguments" add:
-linkskip=System.Threading.Tasks
If that workaround does indeed work, then it's very likely the issue will be fixed in the upcoming service release (due to be released later this week).
Update July 2, 2015
It turns out there is another subtly different common cause of the problem for System.Threading.Tasks. That second bug was originally hidden by Bug 29211 because the two bugs are very similar. The second problem is now being tracked in Xamarin Bug 31560. Note that this bug only affects simulator builds and has fairly simple workarounds, so it is minor in severity.

Got LoaderExceptions in setting specflow 1.9 in for WindowsPhone

I tried to follow
https://github.com/Expensify/WindowsPhoneTestFramework/wiki/Setting-up-a-new-BDD-machine
to setup Specflow on WindowsPhone.
I had a Specflow 1.8.1 installed. so I uninstall 1.8.1 first and install Specflow 1.9 plugin on VS2010.
When running the Specflow. I still got following exception.
[ERROR] Add two numbers: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module)
at System.Reflection.RuntimeModule.GetTypes()
at System.Reflection.Assembly.GetTypes()
at TechTalk.SpecFlow.Bindings.Discovery.RuntimeBindingRegistryBuilder.BuildBindingsFromAssembly(Assembly assembly)
at TechTalk.SpecFlow.Infrastructure.TestExecutionEngine.Initialize(Assembly[] bindingAssemblies)
at TechTalk.SpecFlow.TestRunner.InitializeTestRunner(Assembly[] bindingAssemblies)
at TechTalk.SpecFlow.Infrastructure.TestRunnerFactory.Create(Assembly testAssembly)
at TechTalk.SpecFlow.TestRunnerManager.CreateTestRunner(TestRunnerKey key)
at TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(TestRunnerKey key)
at TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(Assembly testAssembly, Boolean async)
at TechTalk.SpecFlow.TestRunnerManager.GetTestRunner()
at ClassLibrary1.SpecFlowFeature1Feature.FeatureSetup() in C:\source\PhoneApp1\ClassLibrary1\SpecFlowFeature1.feature.cs:line 0
at TechTalk.SpecRun.Framework.TaskExecutors.StaticOrInstanceMethodExecutor.ExecuteInternal(TestThreadExecutionContext testThreadExecutionContext) in c:\TeamCity\buildAgent\work\1ace6ed01d0a43bb\TechTalk.SpecRun.Framework\TaskExecutors\StaticOrInstanceMethodExecutor.cs:line 40
at TechTalk.SpecRun.Framework.TaskExecutors.StaticOrInstanceMethodExecutor.Execute(TestThreadExecutionContext testThreadExecutionContext) in c:\TeamCity\buildAgent\work\1ace6ed01d0a43bb\TechTalk.SpecRun.Framework\TaskExecutors\StaticOrInstanceMethodExecutor.cs:line 21
at TechTalk.SpecRun.Framework.TaskExecutors.ChainedTaskExecutor.Execute(TestThreadExecutionContext testThreadExecutionContext) in c:\TeamCity\buildAgent\work\1ace6ed01d0a43bb\TechTalk.SpecRun.Framework\TaskExecutors\ChainedTaskExecutor.cs:line 20
at TechTalk.SpecRun.Framework.TestThreadExecutor.ExecuteTestNodeTask(TestNode testNode, ITaskExecutor task, TraceEventType eventType) in c:\TeamCity\buildAgent\work\1ace6ed01d0a43bb\TechTalk.SpecRun.Framework\TestThreadExecutor.cs:line 220
The internal exception is LoaderExceptions include
{"Could not load file or assembly 'TechTalk.SpecFlow, Version=1.8.1.0, Culture=neutral, PublicKeyToken=0778194805d6db41' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)":"TechTalk.SpecFlow, Version=1.8.1.0, Culture=neutral, PublicKeyToken=0778194805d6db41"}
I don't know why it still load 1.8.1 SpecFlow assembly. I have uninstalled the SpecFlow 1.8.1. Is there any other place I need to change manually?
Thanks!
The WP7Test package seems to have a dependency to SpecFlow 1.8.1. As far as i see on the github project, it has not been updated yet to SpecFlow 1.9.
SpecRun.SpecFlow 1.1 requires SpecFlow 1.9. (This will be used if you install the obsolete SpecRun (1.0) package.)
I think the best would be to fork the WP7Test project on github and update it to use SpecFlow 1.9. After doing this it should also work fine with the latest SpecRun.
(An alternative way would be to use SpecRun.SpecFlow 1.0 package that works with SpecFlow 1.8.1 and also supported by the SpecFlow 1.9 IDE integration.)

Debugging mscorlib in .Net 4.0

I'm getting the following exception from System.IO.Path.CheckInvalidPathChars() in mscorlib:
[ArgumentException: Illegal characters
in path.]
System.IO.Path.CheckInvalidPathChars(String
path) +142
System.IO.Path.NormalizePath(String
path, Boolean fullCheck, Int32
maxPathLength) +100
System.IO.Path.GetFullPath(String
path) +187
System.Xml.XmlResolver.ResolveUri(Uri
baseUri, String relativeUri) +114
System.Xml.XmlTextReaderImpl..ctor(String
url, XmlNameTable nt) +135
System.Xml.XmlDocument.Load(String
filename) +85
Sitecore.Web.UI.WebControls.WebEditRibbon.ConvertToJson(String
layout) +210
Sitecore.Web.UI.WebControls.WebEditRibbon.Render(HtmlTextWriter
output, Item item) +1268
Sitecore.Web.UI.WebControl.Render(HtmlTextWriter
output) +387
System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter
writer, ICollection children) +246
System.Web.UI.HtmlControls.HtmlForm.RenderChildren(HtmlTextWriter
writer) +315
System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter
writer) +48
System.Web.UI.Control.RenderControlInternal(HtmlTextWriter
writer, ControlAdapter adapter)
+11279890 System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter
writer, ICollection children) +246
System.Web.UI.Page.Render(HtmlTextWriter
writer) +40
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean
includeStagesAfterAsyncPoint) +5274
The thing is, I don't what the path value is that's causing this error. It would help if I could debug the method so I can see the value of the path parameter. I enabled stepping into the .Net Framework code in Visual Studio 2010. I've also loaded the related .Net Framework Symbols from the Microsoft Symbol Servers. However, it seems these PDBs don't include the source; so I can't step into CheckInvalidPathChars and retrieve the path value.
Is it possible to debug mscorlib and step through its source?
Relevant info:
.Net Framework 4.0.
Visual Studio 2010
Any constructive input is greatly appreciated.
Thanks,
Frank
You can get the reference source for the .NET libraries.
http://referencesource.microsoft.com/
Looking at your stacktrace, the problem appears to be originating in Sitecore.Web.UI.WebControls.WebEditRibbon.ConvertToJson. That thing is trying to load an XML file.
Using reflector would allow you to do that.
Is it possible that you enabled to break on all exceptions? Doing that would certainly account for internal exceptions showing up in the debugger. If this is the case, you can safely ignore the exception.
Well mscorlib.dll on your machine is of release build so even though you can very well debug into it, you won't be able to see values local variables/objects etc. The code in this binary is optimized. If you want perfect debugging experience of Microsoft .NET code then you will need to install debug version of .NET on your machine.

Resources