Error installing Visual Studio Express: "failed to open XML file" - visual-studio-express

I'm trying to get my feet into ASP.NET, and so, I began by trying to install Visual Studio Express from http://www.asp.net/get-started, and it gives me
error 25541 - failed to open XML file
I've been trying at this since the past two hours, and I've absolutely no idea how to fix this. Any help?

Try these solutions.
Re-register msxml3.dll by running regsvr32 msxml3.dll
Re-install MSXML3 by downloading and installing the package from http://www.microsoft.com/downloads/details.aspx?familyid=28494391-052b-42ff-9674-f752bdca9582

Related

I cannot install Blazorise in my Blazor server side app. I get the Error that "Microsoft.AspNetCore.Blazor" package could not be find

I have a blazor server side app that is working without problem. (Net Core 3.1). I tried to install Blazorise according the quick start page in https://blazorise.com/docs/start. As my server has no internet access I have downloaded the packages "Blazorise.Bootstrap 0.7.2" and "Blazorise.Icons.FontAwesome 0.9.2.5".
I can install the "Blazorise.Icons.FontAwesome" without Error. But if I try to install "Blazorise.Bootstrap" I get the Error
"NU1101: Unable to find package Microsoft.AspNetCore.Blazor. No packages exist with this id in source(s): Microsoft Visual Studio Offline Packages, Package source"
I cannot find any package like "Microsoft.AspNetCore.Blazor". What should I do now?
Update1:
I have found a package like "Microsoft.AspNetCore.Blazor.Templates 3.1.0-preview4.19579.2" but if I try to install I get Error
"Package 'Microsoft.AspNetCore.Blazor.Templates 3.1.0-preview4.19579.2' has a package type 'Template' that is not supported by project 'WebApplication7'"
I had some problmes at the beginning with updateing NetCore3.1 to Net6.0 But at the end I fixed them. So I could install Blazorise's last version without problem.
Thanks for the comments, suggesting that.

Chrome debugger in Visual Studio Code gets stuck

If I try to start debugging in Visual Studio Code, I get the following error:
No matter what launch.json I use I always get this error. Tried a lot of launch.json configuration. Don't know why it tries to load localhost:9876/debug.html when I set the url to localhost:8100.
My app is running on 8100 port. Debugger for Chrome is plugin is installed. How could I get rid of this error?
The fix was quite easy. For a long time I did not make a restart to my computer. After a computer restart the debug is working now.

Trying to run a HTML application but server could not find right bundle

I tried to run a HTML file that I coded on netbeans in eclipse. I downloaded the web tools platform in the eclipse marketplace. Then I configured the server but when I tried to run the file, I got a popup box with an error saying:
'Starting J2EE Preview at localhost' has encountered a problem. Could not find the required bundle org.eclipse.jetty.webapp. Does anyone know where I could get this bundle. I have eclipse luna.

"The binary code for the script is not found"

I used the script found here
... And every time that I generate this dynamic package, it needs to open the script task and click "Ok" because the "The binary code for the script is not found." error aways appears. Is there a way to solve this without BIDS ? Thanks and sorry my bad english.
I got this error when a SSISDB was upgraded to 2016 from 2012 and the package was not re-deployed using newer visual studio with project set to deploy to SQL Server 2016 in the project deployment properties.
This is often caused to to an error or omission in the code in the script task. If you are certain that the code is correct you can go to the script properties and set the PrecompileiIntoBindaryCode to False, the default is set to true. This is under the Properties or in the Script option of the properties window.
This worked for us
From Project properties, change TargetServerVersion to SQL Server 2019 (Or desired version)
open the .dtsx file for each package in Notepad++ or other text editor
remove the following for each dtsx file (there will be 1 occurence per script component in packages)
<PropertyGroup>
<TargetFrameworkVersion>v4.0</TargetFrameworkVersion>
</PropertyGroup>
save the .dtsx file
go back into Visual Studio and rebuild the project file (as well rebuild individual script task)
I just ran into this error, after I changed my package deployment configuration to 2012. In the script some references we no longer linked. I had to reset the version of the .Net framework in the VS script environment, references were now legit, rebuild success.
In Visual Studio 2017, SSIS 2017 solution, had same error on a script task. Compared to another solution with similar process and discovered the issue was the Reference which had an error did not have a path listed for the dll. Removed the reference and added again. This resolved the issues.
Uninstall VS 2015 and SSDT 14.
Re Install VS 2015 and SSDT 14.
Open a new Integration project and import the SSIS project using the ispac file
Open the task having the error
Click On Edit Script.
Then either do this:
In Build tab click on Run code analysis on solution or Build or Clean and then Build
Save All the solution
Close the window
Click on OK in the task window.
OR just click on edit script and then OK button
The error should go off
This is for Visual Studio 2015 Community/SSDT 14
use SSMS V17.8.1 and upgrade your SSISDB and it will work, I tried it.
For me, I found that using string interpolation caused the issue.
For example:
This line caused the error:
command += $"test {property.Name}";
Changing it to this fixed the error:
command += "test " + property.Name;
After changing from VS 2017 to VS 2019, I saw this error in SQL Server / Integration Services Catalog / "My Package" / Validate... These messages are also visible in Standard Reports / All Executions.
My particular error messages were "VS_ISBROKEN" in the SSIS.Pipeline and "The binary code for the script is not found." in my scripting task.
I opened up the scripting task (C#) and changed the project target to x86 instead of None (MSIL), rebuilt it, closed the scripting solution, pressed Ok to keep the script changes, saved, built and deployed.
That worked for me.
Addendum:
It turns out that I was deploying a single package using VS2019 while the original Project was deployed using VS2017.
I think that the two deployments are not 100% compatible, and recommend that users either deploy an entire project, or deploy a package update using the same version as was used for the initial release.
You should probably ignore my suggestion above about changing project target.
Check your references, make sure all external references are added to the server's GAC.
For adding your dll(for example csvhelper.dll) in GAC you can use the following command in cmd.
C:\test>"C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.7 Tools\gacutil.exe" -i csvhelper.dll
**Put your dll in a folder (for example in test folder)
**Pay attention which version of .Netframework you have(Here I used .net4.7)

Marmalade: error LNK1181: cannot open input file 'python.lib

I'm trying to build Marmalade project for Windows Phone 8 in Visual Studio Ultimate 2012 but receive following error:
error LNK1181: cannot open input file 'python.lib'
Seems that it happens because of wrong path to project's additional library directories. Currently it's c:\users\*user_name_omitted*\appdata\roaming\marmalade\packages\6.3.0\python_2.6.4\lib\wp8\x86
But in fact there is no wp8 folder. As I understand this foulder should be created automatically...
I have Marmalade evaluation license.
How can i get rid ot this error?
Two suggestions:
I've not got a working version to hand, but the bundled version of python with marmalade is (IIRC) 2.5.x, so the reference to 2.6.4 looks odd. I wonder if when you ran s3eConfig it was running a different version and got confused? More as like it should have downloaded some extra stuff and has not.
It might be worth uninstalling marmalade and then re-installing. There are reports of people not having a full installation following the install.