Quantcast
Channel: ScintillaNET Forum Rss Feed
Viewing all articles
Browse latest Browse all 296

New Post: NuGet package?

$
0
0
Hi

you can realize your nuget package anyway. When you create a nuget package, you can specify a folder where your lexer files are. This folder will be included into the nuget package. When a client references the Nuget ScintillaNET package only the scintillanet.dll will be referenced. Developer then have to create a post-build definition (e.g. copy "$(ProjectDir)..\packages\ScintillaNET.2.6.0.0\runtime\SciLexer.dll" "$(TargetDir)") to copy the correct lexer from the extracted nuget package.


A possible nuget spec could look like this:
<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
    <metadata>
        <id>ScintillaNET</id>
        <version>2.6.0.0</version>
        <authors>see: https://scintillanet.codeplex.com/team/view</authors>
        <licenseUrl>https://scintillanet.codeplex.com/license</licenseUrl>
        <projectUrl>https://scintillanet.codeplex.com/</projectUrl>
        <requireLicenseAcceptance>false</requireLicenseAcceptance>
        <description>ScintillaNET is a powerful text editing control for Windows Forms applications and a managed wrapper around the versatile Scintilla component.</description>
    </metadata>
    <files>
        <file src="lib\ScintillaNET.dll" target="lib\ScintillaNET.dll" />
        <file src="lib\ScintillaNET.pdb" target="lib\ScintillaNET.pdb" />
        <file src="lib\ScintillaNET.xml" target="lib\ScintillaNET.xml" />
        <file src="lexer\SciLexer.dll" target="lexer\SciLexer.dll" />
        <file src="lexer\SciLexer64.dll" target="lexer\SciLexer64.dll" />
    </files>
</package>

Viewing all articles
Browse latest Browse all 296

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>