#develop (short for SharpDevelop) is a free IDE for .NET programming languages.

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tree: f7f3b65bd2

4.0

4.1

4.2

4.x

addin-manager-package-subdirectories

filemodels

formsdesignerappdomain

master

newNR

newNRILSpyDebugger

newNRvisualizers

nuget-3.0-ctp

reports

shortcuts

2.0-Beta1

2.0-Beta2

2.0-Beta3

2.0-RC1

2.0-RC2

2.0.0

2.0.1

2.1-Beta1

2.1-Beta2

2.1-Beta3

2.1-RC1

2.1.0

2.2.0

2.2.1

2.2.1b

3.0-Beta1

3.0-Beta2

3.0-Beta3

3.0-RC

3.0.0

3.1-Beta1

3.1-RC1

3.1-RC2

3.1.0

3.1.1

3.2-RC1

3.2-RC2

3.2.0

3.2.1

4.0-Beta1

4.0-Beta2

4.0-Beta3

4.0-Beta4

4.0-RC1

4.0-RC2

4.0.0

4.1-Beta

4.1-RC

4.1.0

4.2-Beta1

4.2-Beta2

4.2-RC1

4.2.0

4.2.1

4.2.2

4.3-Beta1

4.3.0

4.3.1

4.3.2

4.3.3

4.4.0

4.4.1

5.0-Beta1

5.0-Beta2

5.0-Beta3

5.0-Beta4

5.0-Beta5

5.0-RC1

5.0.0

v5.1-archival

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'f7f3b65bd2'

${ noResults }

SharpDevelop/src

History

Matt Ward f7f3b65bd2 Initial port to NuGet 3.0 ... This is an early version that is very broken. Uses a custom build of NuGet 3.0 which targets .NET 4.5: https://github.com/mrward/nuget/tree/3.0-ctp1-net45 Official binaries target .NET 4.5.1 so they cannot be used with SharpDevelop. NuGet binaries are not added to source control since this branch is still a work in progress. So NuGet will need to be compiled from source and the binaries copied to the RequiredLibraries directory. It looks like SharpDevelop may get the automatic rollback that happens in Visual Studio when a package fails to install since it looks like the code is now in NuGet.Core. What works: Installing a package. Uninstalling a package. Updating a package. Issues: 1. Uninstalling/updating does not remove the old files from the packages directory. 2. Managing at the solution level is not implemented. 3. Fails to connect to new NuGet 3.0 feed. Getting an Http version not supported error back from the NuGet 3.0 package source. 4. Unit tests do not compile due to various API changes.		11 years ago
..
AddIns	Initial port to NuGet 3.0	11 years ago
Libraries	Fix #284 NotSupportedException thrown in NR CecilLoader	11 years ago
Main	fix #496: ContextActionBulbControl: it should always be displayed inside the editor's view port bounds	11 years ago
Setup	Fix ReflectionTypeLoadException in WPF designer.	11 years ago
Tools	Adjust StressTest to SD5 API change	11 years ago
Automated.proj	For ToolsVersion="12.0" projects, use the MSBuild 12.0 engine.	11 years ago