https://sourceforge.net/p/pythonnet/code/2013-04-08T09:36:25.169000ZRecent changes to Code repository in pythonnet project2013-04-08T09:36:25.169000Z2013-04-08T09:36:25.169000Zbarton_chttps://sourceforge.net/u/userid-None/https://sourceforge.net2bab70923bb07ed9a8d7ec651128b0d885760ae8

<div class="markdown_content"><h1 id="bugfix-accommodate-new-output-path-x86-vs-x64-wzxhzdk0wzxhzdk1view-changeswzxhzdk2">BUGFIX: Accommodate new output path (x86 vs. x64) #<br /><a href="/p/pythonnet/code/159/">View Changes</a></h1></div>

2013-04-08T09:22:44.694000Z2013-04-08T09:22:44.694000Zbarton_chttps://sourceforge.net/u/userid-None/https://sourceforge.net56a3e644dd9155ab2f49ea8026845e2fae98c1e0

<div class="markdown_content"><h1 id="move-debug_print-to-the-properties-build-page-of-the-debugwin-configuration-wzxhzdk0wzxhzdk1view-changeswzxhzdk2">Move DEBUG_PRINT to the Properties-&gt;Build page of the DebugWin Configuration. #<br /><a href="/p/pythonnet/code/158/">View Changes</a></h1></div>

2013-04-08T08:55:07.408000Z2013-04-08T08:55:07.408000Zbarton_chttps://sourceforge.net/u/userid-None/https://sourceforge.netaea193427ff39df6a0bfae57525cd38bfa7108c6

<div class="markdown_content"><h1 id="fixed-sln-and-csproj-file-configurations-x86x64-monowin-debugrelease-all-reflected-throughout-added-conditional-reference-wzxhzdk0-wzxhzdk1-elements-to-pythonruntimecsproj-building-for-mono-on-windows-added-required-reference-assemblies-building-for-mono-on-windows-wzxhzdk2wzxhzdk3view-changeswzxhzdk4">FIXED: .sln and .csproj file configurations x86/x64 Mono/Win Debug/Release all reflected throughout # # Added Conditional Reference elements to Python.Runtime.csproj =&gt; building for Mono on Windows # # Added Required reference assemblies =&gt; building for Mono on Windows #<br /><a href="/p/pythonnet/code/157/">View Changes</a></h1></div>

2013-01-28T12:10:55.627000Z2013-01-28T12:10:55.627000Zbarton_chttps://sourceforge.net/u/userid-None/https://sourceforge.net0eb542e0c1caa6158e2feb88be95f14097df2f94

<div class="markdown_content"><p>Of course, for the previous to work, you'll be needing the project files to go with... But we don't need another copy of that signing key laying around.<br /><a href="/p/pythonnet/code/156/">View Changes</a></p></div>

2013-01-28T11:55:16.079000Z2013-01-28T11:55:16.079000Zbarton_chttps://sourceforge.net/u/userid-None/https://sourceforge.net50217d496661f968c595c8db41a8325e18f450ed

<div class="markdown_content"><h1 id="solution-configurations-for-each-vs-and-md-well-release-x86-and-x64-binaries-separately-monodevelop-will-now-share-the-solution-and-project-files-with-visual-studio-quite-nicely-in-fact-md-refers-to-mds-files-as-md-1x-solution-files-separate-configs-supports-different-character-widths-on-each-os-platform-platform-specific-settings-are-due-in-part-to-the-introduction-of-dllexports-requirement-which-actually-only-applies-on-windows-hmmm-perhaps-the-linux-guy-will-want-to-revert-to-any-cpu-wzxhzdk0wzxhzdk1view-changeswzxhzdk2">Solution Configurations for each VS and MD - We'll release x86 and x64 binaries separately. # MonoDevelop will now share the solution and project files with Visual Studio quite nicely. In fact, MD refers to .mds files as MD 1.x Solution Files. Separate configs supports different character widths on each OS platform. Platform specific settings are due, in part, to the introduction of DllExport's requirement (which actually only applies on Windows) Hmmm... Perhaps the Linux guy will want to revert to Any CPU #<br /><a href="/p/pythonnet/code/155/">View Changes</a></h1></div>

2013-01-28T10:47:10.327000Z2013-01-28T10:47:10.327000Zbarton_chttps://sourceforge.net/u/userid-None/https://sourceforge.neta89ee97346d38e1747ea79fa193d404027ca526d

<div class="markdown_content"><h1 id="nunit-issues-begin-to-resolve-themselves-amazing-really-since-md-supports-nuget-now-just-grab-nunit-and-add-it-to-packages-honestly-though-i-did-have-to-trick-nuget-into-giving-me-the-unmanagedexport-updatewzxhzdk0wzxhzdk1view-changeswzxhzdk2">NUnit issues begin to resolve themselves (amazing, really) since MD supports NuGet now, just grab NUnit and add it to /packages/. Honestly, though, I did have to trick NuGet into giving me the UnmanagedExport update.<br /><a href="/p/pythonnet/code/154/">View Changes</a></h1></div>

2013-01-28T08:27:40.338000Z2013-01-28T08:27:40.338000Zbarton_chttps://sourceforge.net/u/userid-None/https://sourceforge.netaaa20f41017a0156953d727d496e3b7ddaaa7b4d

<div class="markdown_content"><h1 id="visual-studio-2010-net-40-with-a-little-resharper-thrown-in-the-new-c-clrmodule-depends-on-rgieseckedllexport-in-new-pythonnetpackages-directory-which-was-import-via-nuget-the-signing-key-finally-landed-in-the-correct-directory-not-sure-why-the-consoleconsolecsproj-referenced-pythontest-pythonruntime-assembly-version-bumped-to-4001-tool-and-framework-versions-all-bumped-for-net-40-obsolete-buildclrmodulebat-got-a-tiny-note-after-cli-research-on-clrmoduleil-wzxhzdk0wzxhzdk1view-changeswzxhzdk2">Visual Studio 2010 .NET 4.0 (with a little ReSharper thrown in) # # The new C# clrmodule depends on RGiesecke.DllExport in new pythonnet/packages directory which was import via NuGet # # The signing key finally landed in the correct directory # # Not sure why the console/Console.csproj referenced Python.Test # # Python.Runtime Assembly version bumped to 4.0.0.1 # # Tool and Framework versions all bumped for .NET 4.0 # # <a class="alink" href="../Obsolete?">[Obsolete?]</a> buildclrmodule.bat got a tiny note after cli research on clrmodule.il #<br /><a href="/p/pythonnet/code/153/">View Changes</a></h1></div>

2013-01-28T07:41:24.991000Z2013-01-28T07:41:24.991000Zbarton_chttps://sourceforge.net/u/userid-None/https://sourceforge.net7ff7e4e15a584d5af78e1bed8bf6dc0265741804

<div class="markdown_content"><p>NOTE: All this maintenance led to the soon-to-be-committed DllExport enable module: # Cleanup after much ildasm and research: .fixup, .vtentry, etc. are all handled by the build system since late .NET 2.0. So there's no need to import the platform any longer. There's no fear of conflict with Linux - Mono needs a completely different mechanism (clr.so) to get the "Late Binding" ball rolling. # # There is a big chunk of notes taken regarding my findings #<br /><a href="/p/pythonnet/code/152/">View Changes</a></p></div>

2013-01-27T22:29:16.581000Z2013-01-27T22:29:16.581000Zbarton_chttps://sourceforge.net/u/userid-None/https://sourceforge.net25d95e0a7575565d88c0b0ac4e6e55532c05f49d

<div class="markdown_content"><h1 id="add-signing-key-wzxhzdk0wzxhzdk1view-changeswzxhzdk2">Add Signing Key #<br /><a href="/p/pythonnet/code/151/">View Changes</a></h1></div>

2013-01-27T13:43:05.868000Z2013-01-27T13:43:05.868000Zbarton_chttps://sourceforge.net/u/userid-None/https://sourceforge.net9310f85b644abe6a8b3268c91f77bd65ce8f6080

<div class="markdown_content"><p>Added new usage on "Overloads"<br /><a href="/p/pythonnet/code/150/">View Changes</a></p></div>