I am new in Xamarian cross platform.I am unable to install any package in my project.
I need ITextSharp package to install in my project.
Any suggestion about my project.
or is there any installation error my visual studio 2017 V15.6.6
Here you find my project backup.
https://transfer.pcloud.com/download.html?code=5Z1KYY7Z1tqniyz5QUVZDoDVZswIUny3aQ8BrUrsQ9o7s1z6iCPtk
Please give me suggestion.
You could refer to the following document:
iTextSharp: Any support for dotnet core (netstandard1.6)?
iTextSharp with a Windows 10 Universal App
As you could find in the document, the problem that .NET Standard is not supported by iTextSharp.
iText Software has published a Xamarin port of iText 7, which will continue to get updates. I think you could use itext7 instead, I have tested it on my side, I could install the itext7 without any problem.
Related
ive been having trouble trying to install razor runtime compilation and i continue to get a fault. i updated the vs2019 community edition and was able to click on the checkbox to add the "runtime compilation". when the project is loading, it doesnt install the "razor runtime compliation" package. it doesnt allow me to search for it via NuGet anymore either.
I tried my best to search around and some made it seem very simple to just install it from the pack manager or NuGet. Im using asp.net core 3.1 and vs2019 16.6.1 community edition.
EDIT: HOW CAN I INSTALL ...razor.runtimecompilation.i have not been able to figure out a solution to the error.
"Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation"
This package is from nuget.org in my visual studio. While from your screenshot, it retrive from http://packagesource. Maybe you should configure your package source:
there is a problem.
I've instaled VS 2015 Community version. I wanted to open the project from another computer and there is a problem with it.
Error:
1. Could not find SDK "SQLite.WP81, Version=3.12.2".
Warnings:
1. The referenced component 'SQLite for Windows Phone 8.1' could not be found.
2. Warning IDE0006 Error encountered while loading the project. Some project features, such as full solution analysis for the failed
project and projects that depend on it, have been disabled.
What should I do to work on this project on this computer ? How can I download missing SDK ?
P.s. Im going to work on widnows Phone application.
Thx for help!
Your project is missing SQLite For Windows Phone 8.1 library. Download an updated version of SQLite.WP8.1 here https://visualstudiogallery.msdn.microsoft.com/5d97faf6-39e3-4048-a0bc-adde2af75d1b.
Install it and relaunch Visual Studio.
Further information, including complete documentation, may be found at the official web site "http://www.sqlite.org/".
I am trying to publish my Web App in Visual Studio Professional 2013 but getting the following error
I got the same question asked over here but no useful answer.
Can anyone please help
You probably will be using older version, that was having an issue. refer detail [here]
Install the newer web deployment tool, should work.
which .net version are you using.
check web deploy version. if vs has 2 web deploy version, the vs get confuse to take which version. If it has 2 version, just uninstall vs and then instal it along with web deploy. if the Vs has one 1 web deploy version, you uninstall and install the web deploy. It will rectify your problem i hope.
You can refer This link
Check if version 9.0.0.0 of the assembly is installed in GAC. (from the VS2013 developer command prompt) gacutil /l Microsoft.Web.Deployment. Issues like this have occurred in the past where things worked, then after installing an update (or trying to install one) then reports of missing dlls, like nuget, occur.
The usual course of action is to repair the Visual Studio installation.
There is a problem with your publish profile. Delete the pubxml file located bellow Properties folder in your project and then create a new publish profile.
I got the same problem when older project runs into the new .NET Framework, for that you have to do the following.
Right Click on your project name->select Property Pages -> Click Build from the menu-> then select Target Framework .Net framework 4.5 or your current using framework..
"Could not load file or assembly" means the required file (of that mentioned version) is not available in the assembly (nor in the registry). All you gotta to do is to ensure this same is installed properly that would allow you to proceed further. The other things to ensure is the latest framework installed on your system.
Think you have some errors happen when to install or update Visual 2013, so you can reinstall again and this error will be fixed.
I have many .sqlproj projects that need to be built on our build server. I don't want to install all of Visual Studio on the build server just so I can install SSDT to build these. How can I build .sqlproj projects without a full VS install?
Here's the raw error I get on the build server when trying to build without SSDT intstalled:
C:\MyProject\MyProj.sqlproj (4): The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
Answer: Microsoft now has an official NuGet package (see blog post).
Old answer, prior to August 2016; provided in case the NuGet package doesn't work for you:
Install dacframework.msi (x86|x64)
Install SQLDOM.MSI (x86|x64)
Install SQLLS.MSI (x86|x64)
Install SQLSysClrTypes.msi (x86|x64)
Install SSDTBuildUtilities.msi (from the "Administrator Install Point" as setup in step 3 here)
Done!
Source: Headless MSBuild Support for SSDT (*.sqlproj) Projects.
Microsoft SQL Server Data Tools:
http://msdn.microsoft.com/en-us/data/hh297027
Install the tools on build machine to fix the problem.
The Microsoft SQL Server Data Tools team has released a NuGet package named Microsoft.Data.Tools.Msbuild, which helps to build SQL Projects on build servers.
see : https://blogs.msdn.microsoft.com/ssdt/2016/08/22/releasing-ssdt-with-visual-studio-15-preview-4-and-introducing-ssdt-msbuild-nuget-package/
NuGet package : https://www.nuget.org/packages/Microsoft.Data.Tools.Msbuild/
SSDT v12.0.50730.0 requires Visual Studio to be installed beforehand. I found the easiest solution was to install the bare minimum Visual Studio components which were downloaded from MSDN Subscriber downloads:
Visual Studio 2013 Isolated
Visual Studio 2013 Shell
Then SSDT installed fine.
I also used part of the solution outlined above.
* Install dacframework.msi
* Install SQLDOM.MSI
* Install SQLLS.MSI
* Install SQLSysClrTypes.msi
I use MSBuild 12.0 to perform the build which is also available as a separate download.
I was having the exact same issue building a SQL Server project on an Azure DevOps CI/CD pipeline. None of the pre-built build tasks would work for me.
Some answers mention a NuGet package, but I am not sure how can I use it, because SQL Server projects do not allow to install NuGet packages.
I solved this by avoiding to add a SQL Server project to the solution.
I achieved this by using an MSBuild SDK, capable of producing a SQL Server Data-Tier Application package (.dacpac) from the set of SQL scripts. By adding this second project to the solution, I managed to continue taking advantage of linking the project to a live database through SQL Server Object Explorer on Visual Studio. I gave a more detailed explanation about my implementation in this answer.
On specflow's own instalation guide it says that the only way to install it is using the .msi installer and most of the tutorials I've read on the subject tell me to download and install said file but when I search on the nuget package manager I find there's also an available package for specflow.
The difference is in the tooling. With the MSI you get full item template, syntax coloring and intellisense support in the IDE where as with the NuGet you just get the code generation and runtime support. So I'd say 9 times out of 10 if you're going to be doing any serious work with it you're going to want the MSI for those rich features.
At this point they really should be offering it as a Visual Studio Extension for a lot more integrated install experience using VS Extension Manager.