ryujinx/GtkSharp
1
0
Fork 0
mirror of https://github.com/Ryujinx/GtkSharp.git synced 2024-12-23 19:45:37 +00:00
Code Issues Packages Projects Releases Wiki Activity
GtkSharp/gio/gio.csproj

423 lines
24 KiB
XML
Raw Normal View History

Add a MonoDevelop solution and projects for browsing the codebase This is just to be able to use MonoDevelop to browse the codebase, both custom and generated code. It is NOT intended to be used to build anything.
2012-10-13 14:15:46 +00:00
<?xml version="1.0" encoding="utf-8"?>
csproj ToolsVersion to 4.0
2015-06-08 20:33:18 +00:00
<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
Add a MonoDevelop solution and projects for browsing the codebase This is just to be able to use MonoDevelop to browse the codebase, both custom and generated code. It is NOT intended to be used to build anything.
2012-10-13 14:15:46 +00:00
<PropertyGroup>
<Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
<Platform Condition=" '$(Platform)' == '' ">x86</Platform>
<ProductVersion>9.0.21022</ProductVersion>
<SchemaVersion>2.0</SchemaVersion>
<ProjectGuid>{1C3BB17B-336D-432A-8952-4E979BC90867}</ProjectGuid>
MSBuild: change some projects to Library type, not Executable Even though gtk-sharp cannot be built via MSBuild (yet?), it's better to make the .csproj reflect more closely what you get with the normal build.
2013-09-23 23:06:57 +00:00
<OutputType>Library</OutputType>
Add a MonoDevelop solution and projects for browsing the codebase This is just to be able to use MonoDevelop to browse the codebase, both custom and generated code. It is NOT intended to be used to build anything.
2012-10-13 14:15:46 +00:00
<RootNamespace>gio</RootNamespace>
csproj: Fix assembly names and include *.dll.config in output Signed-off-by: Bertrand Lorentz <bertrand.lorentz@gmail.com>
2014-09-21 13:07:38 +00:00
<AssemblyName>gio-sharp</AssemblyName>
Update csproj TargetFrameworkVersion
2015-10-29 14:24:44 +00:00
<TargetFrameworkVersion>v4.0</TargetFrameworkVersion>
<TargetFrameworkProfile />
Add a MonoDevelop solution and projects for browsing the codebase This is just to be able to use MonoDevelop to browse the codebase, both custom and generated code. It is NOT intended to be used to build anything.
2012-10-13 14:15:46 +00:00
</PropertyGroup>
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|x86' ">
<DebugSymbols>true</DebugSymbols>
<DebugType>full</DebugType>
<Optimize>false</Optimize>
<OutputPath>bin\Debug</OutputPath>
<DefineConstants>DEBUG;</DefineConstants>
<ErrorReport>prompt</ErrorReport>
<WarningLevel>4</WarningLevel>
<PlatformTarget>x86</PlatformTarget>
<ConsolePause>false</ConsolePause>
MSBuild: fix the solution build (except audit and sample projects) This commit makes it possible to build any project of the gtk-sharp.sln from an IDE (except audit and sample projects, which require a bit more work). This doesn't mean that autotools is deprecated, but just that it is more comfortable to use an IDE when working on gtk-sharp because it will offer better auto-completion, and will stop highlight misleading semantic errors, from now on.
2013-10-24 10:57:42 +00:00
<AllowUnsafeBlocks>true</AllowUnsafeBlocks>
Add a MonoDevelop solution and projects for browsing the codebase This is just to be able to use MonoDevelop to browse the codebase, both custom and generated code. It is NOT intended to be used to build anything.
2012-10-13 14:15:46 +00:00
</PropertyGroup>
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|x86' ">
<DebugType>none</DebugType>
<Optimize>false</Optimize>
<OutputPath>bin\Release</OutputPath>
<ErrorReport>prompt</ErrorReport>
<WarningLevel>4</WarningLevel>
<PlatformTarget>x86</PlatformTarget>
<ConsolePause>false</ConsolePause>
MSBuild: fix the solution build (except audit and sample projects) This commit makes it possible to build any project of the gtk-sharp.sln from an IDE (except audit and sample projects, which require a bit more work). This doesn't mean that autotools is deprecated, but just that it is more comfortable to use an IDE when working on gtk-sharp because it will offer better auto-completion, and will stop highlight misleading semantic errors, from now on.
2013-10-24 10:57:42 +00:00
<AllowUnsafeBlocks>true</AllowUnsafeBlocks>
Add a MonoDevelop solution and projects for browsing the codebase This is just to be able to use MonoDevelop to browse the codebase, both custom and generated code. It is NOT intended to be used to build anything.
2012-10-13 14:15:46 +00:00
</PropertyGroup>
<Import Project="$(MSBuildBinPath)\Microsoft.CSharp.targets" />
<ItemGroup>
<Compile Include="AppInfoAdapter.cs" />
gio: Track API changes (I- interface prefixes) This includes changes to fix the build, and changes to custom code that gets added to the generated code. I.e. File.cs now becomes IFile.cs
2013-04-01 22:53:50 +00:00
<Compile Include="IFile.cs" />
Add a MonoDevelop solution and projects for browsing the codebase This is just to be able to use MonoDevelop to browse the codebase, both custom and generated code. It is NOT intended to be used to build anything.
2012-10-13 14:15:46 +00:00
<Compile Include="FileAdapter.cs" />
<Compile Include="FileEnumerator.cs" />
<Compile Include="FileFactory.cs" />
<Compile Include="GioStream.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\AcceptCertificateHandler.cs" />
<Compile Include="generated\GLib\ActionAdapter.cs" />
<Compile Include="generated\GLib\ActionAddedHandler.cs" />
<Compile Include="generated\GLib\ActionEnabledChangedHandler.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\ActionEntry.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\ActionGroupAdapter.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\ActionMapAdapter.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\ActionRemovedHandler.cs" />
<Compile Include="generated\GLib\ActionStateChangedHandler.cs" />
<Compile Include="generated\GLib\AppInfoAdapter.cs" />
<Compile Include="generated\GLib\AppInfoCreateFlags.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\AppInfoMonitor.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\AppLaunchContext.cs" />
<Compile Include="generated\GLib\Application.cs" />
<Compile Include="generated\GLib\ApplicationCommandLine.cs" />
<Compile Include="generated\GLib\ApplicationFlags.cs" />
<Compile Include="generated\GLib\AskPasswordFlags.cs" />
<Compile Include="generated\GLib\AskPasswordHandler.cs" />
<Compile Include="generated\GLib\AskQuestionHandler.cs" />
<Compile Include="generated\GLib\AsyncInitableAdapter.cs" />
<Compile Include="generated\GLib\AsyncReadyCallback.cs" />
<Compile Include="generated\GLib\AsyncResultAdapter.cs" />
<Compile Include="generated\GLib\BufferedInputStream.cs" />
<Compile Include="generated\GLib\BufferedOutputStream.cs" />
<Compile Include="generated\GLib\BusNameOwnerFlags.cs" />
<Compile Include="generated\GLib\BusNameWatcherFlags.cs" />
<Compile Include="generated\GLib\BusType.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\BytesIcon.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\Cancellable.cs" />
<Compile Include="generated\GLib\CancellableSourceFunc.cs" />
<Compile Include="generated\GLib\ChangeEventHandler.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\ChangedHandler.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\CharsetConverter.cs" />
<Compile Include="generated\GLib\CommandLineHandler.cs" />
<Compile Include="generated\GLib\ContentType.cs" />
<Compile Include="generated\GLib\ConverterAdapter.cs" />
<Compile Include="generated\GLib\ConverterFlags.cs" />
<Compile Include="generated\GLib\ConverterResult.cs" />
<Compile Include="generated\GLib\Credentials.cs" />
<Compile Include="generated\GLib\CredentialsType.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\DBusActionGroup.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\DBusAnnotationInfo.cs" />
<Compile Include="generated\GLib\DBusArgInfo.cs" />
<Compile Include="generated\GLib\DBusAuthObserver.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\DBusAuthObserverClass.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\DBusCallFlags.cs" />
<Compile Include="generated\GLib\DBusCapabilityFlags.cs" />
<Compile Include="generated\GLib\DBusConnection.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\DBusConnectionClass.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\DBusConnectionFlags.cs" />
<Compile Include="generated\GLib\DBusError.cs" />
<Compile Include="generated\GLib\DBusErrorEntry.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\DBusInterface.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\DBusInterfaceInfo.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\DBusInterfaceSkeleton.cs" />
<Compile Include="generated\GLib\DBusInterfaceSkeletonFlags.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\DBusInterfaceVTable.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\DBusMenuGroup.cs" />
<Compile Include="generated\GLib\DBusMenuPath.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\DBusMessage.cs" />
<Compile Include="generated\GLib\DBusMessageByteOrder.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\DBusMessageClass.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\DBusMessageFlags.cs" />
<Compile Include="generated\GLib\DBusMessageHeaderField.cs" />
<Compile Include="generated\GLib\DBusMessageType.cs" />
<Compile Include="generated\GLib\DBusMethodInfo.cs" />
<Compile Include="generated\GLib\DBusMethodInvocation.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\DBusMethodInvocationClass.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\DBusNodeInfo.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\DBusObject.cs" />
<Compile Include="generated\GLib\DBusObjectManager.cs" />
<Compile Include="generated\GLib\DBusObjectManagerClient.cs" />
<Compile Include="generated\GLib\DBusObjectManagerClientFlags.cs" />
<Compile Include="generated\GLib\DBusObjectManagerServer.cs" />
<Compile Include="generated\GLib\DBusObjectProxy.cs" />
<Compile Include="generated\GLib\DBusObjectSkeleton.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\DBusPropertyInfo.cs" />
<Compile Include="generated\GLib\DBusPropertyInfoFlags.cs" />
<Compile Include="generated\GLib\DBusProxy.cs" />
<Compile Include="generated\GLib\DBusProxyFlags.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\DBusProxyTypeFunc.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\DBusSendMessageFlags.cs" />
<Compile Include="generated\GLib\DBusServer.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\DBusServerClass.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\DBusServerFlags.cs" />
<Compile Include="generated\GLib\DBusSignalFlags.cs" />
<Compile Include="generated\GLib\DBusSignalInfo.cs" />
<Compile Include="generated\GLib\DBusSubtreeFlags.cs" />
<Compile Include="generated\GLib\DBusSubtreeVTable.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\DataInputStream.cs" />
<Compile Include="generated\GLib\DataOutputStream.cs" />
<Compile Include="generated\GLib\DataStreamByteOrder.cs" />
<Compile Include="generated\GLib\DataStreamNewlineType.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\DriveAdapter.cs" />
<Compile Include="generated\GLib\DriveChangedHandler.cs" />
<Compile Include="generated\GLib\DriveConnectedHandler.cs" />
<Compile Include="generated\GLib\DriveDisconnectedHandler.cs" />
<Compile Include="generated\GLib\DriveEjectButtonHandler.cs" />
<Compile Include="generated\GLib\DriveStartFlags.cs" />
<Compile Include="generated\GLib\DriveStartStopType.cs" />
<Compile Include="generated\GLib\DriveStopButtonHandler.cs" />
<Compile Include="generated\GLib\DummyProxyResolver.cs" />
<Compile Include="generated\GLib\DummyTlsCertificate.cs" />
<Compile Include="generated\GLib\DummyTlsCertificateClass.cs" />
<Compile Include="generated\GLib\DummyTlsConnection.cs" />
<Compile Include="generated\GLib\DummyTlsConnectionClass.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\DummyTlsDatabase.cs" />
<Compile Include="generated\GLib\DummyTlsDatabaseClass.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\Emblem.cs" />
<Compile Include="generated\GLib\EmblemOrigin.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\EmblemedIcon.cs" />
<Compile Include="generated\GLib\EventHandler.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\ExportedObject.cs" />
<Compile Include="generated\GLib\ExportedSubtree.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\FdoNotificationBackend.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\FileAdapter.cs" />
<Compile Include="generated\GLib\FileAttributeInfo.cs" />
<Compile Include="generated\GLib\FileAttributeInfoFlags.cs" />
<Compile Include="generated\GLib\FileAttributeInfoList.cs" />
<Compile Include="generated\GLib\FileAttributeMatcher.cs" />
<Compile Include="generated\GLib\FileAttributeStatus.cs" />
<Compile Include="generated\GLib\FileAttributeType.cs" />
<Compile Include="generated\GLib\FileChange.cs" />
<Compile Include="generated\GLib\FileCopyFlags.cs" />
<Compile Include="generated\GLib\FileCreateFlags.cs" />
<Compile Include="generated\GLib\FileDescriptorBasedAdapter.cs" />
<Compile Include="generated\GLib\FileEnumerator.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\FileIOStream.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\FileIcon.cs" />
<Compile Include="generated\GLib\FileInfo.cs" />
<Compile Include="generated\GLib\FileInputStream.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\FileMeasureFlags.cs" />
<Compile Include="generated\GLib\FileMeasureProgressCallback.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\FileMonitor.cs" />
<Compile Include="generated\GLib\FileMonitorEvent.cs" />
<Compile Include="generated\GLib\FileMonitorFlags.cs" />
<Compile Include="generated\GLib\FileOutputStream.cs" />
<Compile Include="generated\GLib\FileProgressCallback.cs" />
<Compile Include="generated\GLib\FileQueryInfoFlags.cs" />
<Compile Include="generated\GLib\FileReadMoreCallback.cs" />
<Compile Include="generated\GLib\FileType.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\FilenameCompleter.cs" />
<Compile Include="generated\GLib\FilesystemPreviewType.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\FilterInputStream.cs" />
<Compile Include="generated\GLib\FilterOutputStream.cs" />
<Compile Include="generated\GLib\GLibSharp.AsyncReadyCallbackNative.cs" />
<Compile Include="generated\GLib\GLibSharp.CancellableSourceFuncNative.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\GLibSharp.DBusProxyTypeFuncNative.cs" />
<Compile Include="generated\GLib\GLibSharp.FileMeasureProgressCallbackNative.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\GLibSharp.FileProgressCallbackNative.cs" />
<Compile Include="generated\GLib\GLibSharp.FileReadMoreCallbackNative.cs" />
<Compile Include="generated\GLib\GLibSharp.GSourceFuncNative.cs" />
<Compile Include="generated\GLib\GLibSharp.IOSchedulerJobFuncNative.cs" />
<Compile Include="generated\GLib\GLibSharp.PollableSourceFuncNative.cs" />
<Compile Include="generated\GLib\GLibSharp.ReallocFuncNative.cs" />
<Compile Include="generated\GLib\GLibSharp.SettingsBindGetMappingNative.cs" />
<Compile Include="generated\GLib\GLibSharp.SettingsBindSetMappingNative.cs" />
<Compile Include="generated\GLib\GLibSharp.SettingsGetMappingNative.cs" />
<Compile Include="generated\GLib\GLibSharp.SimpleAsyncThreadFuncNative.cs" />
<Compile Include="generated\GLib\GLibSharp.SocketSourceFuncNative.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\GLibSharp.SpawnChildSetupFuncNative.cs" />
<Compile Include="generated\GLib\GLibSharp.TaskThreadFuncNative.cs" />
<Compile Include="generated\GLib\GioGlobal.cs" />
<Compile Include="generated\GLib\GtkNotificationBackend.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\IAction.cs" />
<Compile Include="generated\GLib\IActionGroup.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\IActionMap.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\IAppInfo.cs" />
<Compile Include="generated\GLib\IAsyncInitable.cs" />
<Compile Include="generated\GLib\IAsyncResult.cs" />
<Compile Include="generated\GLib\IConverter.cs" />
<Compile Include="generated\GLib\IDrive.cs" />
<Compile Include="generated\GLib\IFile.cs" />
<Compile Include="generated\GLib\IFileDescriptorBased.cs" />
<Compile Include="generated\GLib\IIcon.cs" />
<Compile Include="generated\GLib\IInitable.cs" />
<Compile Include="generated\GLib\ILoadableIcon.cs" />
<Compile Include="generated\GLib\IMount.cs" />
<Compile Include="generated\GLib\IOError.cs" />
<Compile Include="generated\GLib\IOErrorEnum.cs" />
<Compile Include="generated\GLib\IOExtension.cs" />
<Compile Include="generated\GLib\IOExtensionPoint.cs" />
<Compile Include="generated\GLib\IOModule.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\IOModuleScope.cs" />
<Compile Include="generated\GLib\IOModuleScopeFlags.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\IOSchedulerJob.cs" />
<Compile Include="generated\GLib\IOSchedulerJobFunc.cs" />
<Compile Include="generated\GLib\IOStream.cs" />
<Compile Include="generated\GLib\IOStreamAdapter.cs" />
<Compile Include="generated\GLib\IOStreamSpliceFlags.cs" />
<Compile Include="generated\GLib\IProxy.cs" />
<Compile Include="generated\GLib\IProxyResolver.cs" />
<Compile Include="generated\GLib\ISeekable.cs" />
<Compile Include="generated\GLib\ISocketConnectable.cs" />
<Compile Include="generated\GLib\ITlsClientConnection.cs" />
<Compile Include="generated\GLib\ITlsServerConnection.cs" />
<Compile Include="generated\GLib\IVolume.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\IconAdapter.cs" />
<Compile Include="generated\GLib\IncomingHandler.cs" />
<Compile Include="generated\GLib\InetAddress.cs" />
<Compile Include="generated\GLib\InetAddressMask.cs" />
<Compile Include="generated\GLib\InetSocketAddress.cs" />
<Compile Include="generated\GLib\InitableAdapter.cs" />
<Compile Include="generated\GLib\InputStream.cs" />
<Compile Include="generated\GLib\InputVector.cs" />
<Compile Include="generated\GLib\ItemsChangedHandler.cs" />
<Compile Include="generated\GLib\LaunchedFailedHandler.cs" />
<Compile Include="generated\GLib\LaunchedHandler.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\LoadableIconAdapter.cs" />
<Compile Include="generated\GLib\LocalDirectoryMonitor.cs" />
<Compile Include="generated\GLib\LocalFileEnumerator.cs" />
<Compile Include="generated\GLib\LocalFileIOStream.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\MemoryBuffer.cs" />
<Compile Include="generated\GLib\Menu.cs" />
<Compile Include="generated\GLib\MenuAttributeIter.cs" />
<Compile Include="generated\GLib\MenuExporter.cs" />
<Compile Include="generated\GLib\MenuExporterGroup.cs" />
<Compile Include="generated\GLib\MenuExporterLink.cs" />
<Compile Include="generated\GLib\MenuExporterMenu.cs" />
<Compile Include="generated\GLib\MenuExporterRemote.cs" />
<Compile Include="generated\GLib\MenuExporterWatch.cs" />
<Compile Include="generated\GLib\MenuItem.cs" />
<Compile Include="generated\GLib\MenuLinkIter.cs" />
<Compile Include="generated\GLib\MenuModel.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\MessageToWriteData.cs" />
<Compile Include="generated\GLib\MountAdapter.cs" />
<Compile Include="generated\GLib\MountAddedHandler.cs" />
<Compile Include="generated\GLib\MountChangedHandler.cs" />
<Compile Include="generated\GLib\MountMountFlags.cs" />
<Compile Include="generated\GLib\MountOperation.cs" />
<Compile Include="generated\GLib\MountOperationResult.cs" />
<Compile Include="generated\GLib\MountPreUnmountHandler.cs" />
<Compile Include="generated\GLib\MountRemovedHandler.cs" />
<Compile Include="generated\GLib\MountUnmountFlags.cs" />
<Compile Include="generated\GLib\NativeVolumeMonitor.cs" />
<Compile Include="generated\GLib\NetworkAddress.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\NetworkMonitor.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\NetworkService.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\NextstepSettingsBackend.cs" />
<Compile Include="generated\GLib\Notification.cs" />
<Compile Include="generated\GLib\NotificationBackend.cs" />
<Compile Include="generated\GLib\NotificationPriority.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\OpenedHandler.cs" />
<Compile Include="generated\GLib\OutputStream.cs" />
<Compile Include="generated\GLib\OutputStreamSpliceFlags.cs" />
<Compile Include="generated\GLib\OutputVector.cs" />
<Compile Include="generated\GLib\PasswordSave.cs" />
<Compile Include="generated\GLib\Permission.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\Pollable.cs" />
<Compile Include="generated\GLib\PollableInputStream.cs" />
<Compile Include="generated\GLib\PollableOutputStream.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\PollableSourceFunc.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\PropertyAction.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\ProxyAdapter.cs" />
<Compile Include="generated\GLib\ProxyAddress.cs" />
<Compile Include="generated\GLib\ProxyAddressEnumerator.cs" />
<Compile Include="generated\GLib\ProxyResolverAdapter.cs" />
<Compile Include="generated\GLib\ReallocFunc.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\RemoteActionGroup.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\ReplyHandler.cs" />
<Compile Include="generated\GLib\Resolver.cs" />
<Compile Include="generated\GLib\ResolverError.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\ResolverRecordType.cs" />
<Compile Include="generated\GLib\Resource.cs" />
<Compile Include="generated\GLib\ResourceError.cs" />
<Compile Include="generated\GLib\ResourceFileEnumerator.cs" />
<Compile Include="generated\GLib\ResourceFileEnumeratorClass.cs" />
<Compile Include="generated\GLib\ResourceFileInputStream.cs" />
<Compile Include="generated\GLib\ResourceFileInputStreamClass.cs" />
<Compile Include="generated\GLib\ResourceFlags.cs" />
<Compile Include="generated\GLib\ResourceLookupFlags.cs" />
<Compile Include="generated\GLib\Resources.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\RunHandler.cs" />
<Compile Include="generated\GLib\SchemaState.cs" />
<Compile Include="generated\GLib\SeekableAdapter.cs" />
<Compile Include="generated\GLib\Settings.cs" />
<Compile Include="generated\GLib\SettingsBackend.cs" />
<Compile Include="generated\GLib\SettingsBackendClosure.cs" />
<Compile Include="generated\GLib\SettingsBackendWatch.cs" />
<Compile Include="generated\GLib\SettingsBindFlags.cs" />
<Compile Include="generated\GLib\SettingsBindGetMapping.cs" />
<Compile Include="generated\GLib\SettingsBindSetMapping.cs" />
<Compile Include="generated\GLib\SettingsGetMapping.cs" />
<Compile Include="generated\GLib\ShowProcessesHandler.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\ShowUnmountProgressHandler.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\SimpleAction.cs" />
<Compile Include="generated\GLib\SimpleActionGroup.cs" />
<Compile Include="generated\GLib\SimpleAsyncResult.cs" />
<Compile Include="generated\GLib\SimpleAsyncThreadFunc.cs" />
<Compile Include="generated\GLib\SimplePermission.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\SimpleProxyResolver.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\Socket.cs" />
<Compile Include="generated\GLib\SocketAddress.cs" />
<Compile Include="generated\GLib\SocketAddressEnumerator.cs" />
<Compile Include="generated\GLib\SocketClient.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\SocketClientEvent.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\SocketConnectableAdapter.cs" />
<Compile Include="generated\GLib\SocketConnection.cs" />
<Compile Include="generated\GLib\SocketControlMessage.cs" />
<Compile Include="generated\GLib\SocketFamily.cs" />
<Compile Include="generated\GLib\SocketListener.cs" />
<Compile Include="generated\GLib\SocketMsgFlags.cs" />
<Compile Include="generated\GLib\SocketProtocol.cs" />
<Compile Include="generated\GLib\SocketService.cs" />
<Compile Include="generated\GLib\SocketSourceFunc.cs" />
<Compile Include="generated\GLib\SocketType.cs" />
<Compile Include="generated\GLib\Socks4Proxy.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\Socks4aProxy.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\Socks5Proxy.cs" />
<Compile Include="generated\GLib\SrvTarget.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\StaticResource.cs" />
<Compile Include="generated\GLib\Subprocess.cs" />
<Compile Include="generated\GLib\SubprocessFlags.cs" />
<Compile Include="generated\GLib\SubprocessLauncher.cs" />
<Compile Include="generated\GLib\Task.cs" />
<Compile Include="generated\GLib\TaskThreadFunc.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\TcpConnection.cs" />
<Compile Include="generated\GLib\TcpWrapperConnection.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\TestDBus.cs" />
<Compile Include="generated\GLib\TestDBusClass.cs" />
<Compile Include="generated\GLib\TestDBusFlags.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\ThemedIcon.cs" />
<Compile Include="generated\GLib\ThreadedResolver.cs" />
<Compile Include="generated\GLib\ThreadedSocketService.cs" />
<Compile Include="generated\GLib\TlsAuthenticationMode.cs" />
<Compile Include="generated\GLib\TlsCertificate.cs" />
<Compile Include="generated\GLib\TlsCertificateFlags.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\TlsCertificateRequestFlags.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\TlsClientConnectionAdapter.cs" />
<Compile Include="generated\GLib\TlsConnection.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\TlsDatabase.cs" />
<Compile Include="generated\GLib\TlsDatabaseLookupFlags.cs" />
<Compile Include="generated\GLib\TlsDatabaseVerifyFlags.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\TlsError.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\TlsFileDatabase.cs" />
<Compile Include="generated\GLib\TlsInteraction.cs" />
<Compile Include="generated\GLib\TlsInteractionResult.cs" />
<Compile Include="generated\GLib\TlsPassword.cs" />
<Compile Include="generated\GLib\TlsPasswordFlags.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\TlsRehandshakeMode.cs" />
<Compile Include="generated\GLib\TlsServerConnectionAdapter.cs" />
<Compile Include="generated\GLib\UnixConnection.cs" />
<Compile Include="generated\GLib\UnixCredentialsMessage.cs" />
<Compile Include="generated\GLib\UnixFDList.cs" />
<Compile Include="generated\GLib\UnixFDMessage.cs" />
<Compile Include="generated\GLib\UnixSocketAddress.cs" />
<Compile Include="generated\GLib\UnixSocketAddressType.cs" />
<Compile Include="generated\GLib\Vfs.cs" />
<Compile Include="generated\GLib\VolumeAdapter.cs" />
<Compile Include="generated\GLib\VolumeAddedHandler.cs" />
<Compile Include="generated\GLib\VolumeChangedHandler.cs" />
<Compile Include="generated\GLib\VolumeMonitor.cs" />
<Compile Include="generated\GLib\VolumeRemovedHandler.cs" />
<Compile Include="generated\GLib\WritableChangeEventHandler.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="generated\GLib\WritableChangedHandler.cs" />
generator: Create a directory for each namespace When dealing with several namespaces there might be classes with the same name (especially Global which is autogenerated in g-i based bindings). On generation the file would be overriden by the last occurence in the xml. To encounter this every namespace has it's own directory now. This also improves structure a lot when dealing with big libraries. Also do the necessary adaption for the build and the csproj files.
2014-02-24 01:04:03 +00:00
<Compile Include="generated\GLib\ZlibCompressor.cs" />
<Compile Include="generated\GLib\ZlibCompressorFormat.cs" />
<Compile Include="generated\GLib\ZlibDecompressor.cs" />
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<Compile Include="..\AssemblyInfo.cs">
<Link>Properties\AssemblyInfo.cs</Link>
</Compile>
gio: Rename Content class to ContentType and adjust method names The parser automatically groups static functions with the same prefix into classes, but the right name can't be determined automatically. In this case, ContentType.GetDescription(...) is much better than Content.TypeGetDescription(...).
2012-11-11 10:50:49 +00:00
</ItemGroup>
<ItemGroup>
<ProjectReference Include="..\glib\glib.csproj">
<Project>{3BF1D531-8840-4F15-8066-A9788D8C398B}</Project>
<Name>glib</Name>
</ProjectReference>
Add a MonoDevelop solution and projects for browsing the codebase This is just to be able to use MonoDevelop to browse the codebase, both custom and generated code. It is NOT intended to be used to build anything.
2012-10-13 14:15:46 +00:00
</ItemGroup>
MSBuild: fix the solution build (except audit and sample projects) This commit makes it possible to build any project of the gtk-sharp.sln from an IDE (except audit and sample projects, which require a bit more work). This doesn't mean that autotools is deprecated, but just that it is more comfortable to use an IDE when working on gtk-sharp because it will offer better auto-completion, and will stop highlight misleading semantic errors, from now on.
2013-10-24 10:57:42 +00:00
<ItemGroup>
<Reference Include="System" />
</ItemGroup>
Update References file's in csproj
2015-10-29 15:10:23 +00:00
<ItemGroup />
csproj: Fix assembly names and include *.dll.config in output Signed-off-by: Bertrand Lorentz <bertrand.lorentz@gmail.com>
2014-09-21 13:07:38 +00:00
<ItemGroup>
<None Include="gio-sharp.dll.config">
<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
</None>
</ItemGroup>
Update References file's in csproj
2015-10-29 15:10:23 +00:00
</Project>
Reference in a new issue Copy permalink