On Mon, Feb 14, 2011 at 12:05 PM, Quandary wrote:
> What exactly do you need fixed ?
I'd rather discuss that offlist initially.
> If you're searching for an ultra-cheap, ultra-UNreliable solution for
> outsourcing an ultra-work-insentive fix,
> go to
> www.rentacoder.com
Someone who's already c
This stackoverflow question/answer is also interesting in considering
moving the build to xbuild:
http://stackoverflow.com/questions/2472183/replace-sln-with-msbuild-and-wrap-contained-projects-into-targets/2474892#2474892
Rafael "Monoman" Teixeira
---
"We live
Sorry, my memory failed me. VS2010 doesn't support multi-targetting in
the same csproj, also it doesn't honor things like
So you need to keep separate .csproj for each targetted framework. It
seems that there are different .sources files too (as for the
droid/iphone versions of System.Data).
Hello,
>> You can have the csproj reference the .sources file externally, and use a
>> small Task to transform the list of files into Compile elements. This works
>> in VS for building, but does not show the sources as files in the csproj via
>> the UI. So, depending what you want...
Something like
Hello,
> You can have the csproj reference the .sources file externally, and use a
> small Task to transform the list of files into Compile elements. This works
> in VS for building, but does not show the sources as files in the csproj via
> the UI. So, depending what you want...
I wanted to make
AFAIR, VS2010 introduced multi-profile support, in the same project
file. So it may be possible to get rid of .sources and support
building for multiple profiles from .csprojs at the same time.
Rafael "Monoman" Teixeira
---
"We live in a world operated by scienc
You can have the csproj reference the .sources file externally, and use a
small Task to transform the list of files into Compile elements. This works
in VS for building, but does not show the sources as files in the csproj via
the UI. So, depending what you want...
- Jon
On Mon, Feb 14, 2011 at 7
> We could create a simple Task which does .sources to /> on the fly or drop .sources completely and use .csproj only
How would we use this Task?
The only problem with dropping sources and going the .csproj route is
that currently we have at least 2 csproj files per directory (one 2_0,
one 4_0 a
A short interim solution would be a "Hire-A-Bug-Fixer" page in the wiki.
But someone could point to some site that can organize that, possibly,
dynamic list of bug-fixers for hire, and mediate the transactions (Not
sure the current sites/services are up to the task, as they seem too
noisy). Some e
Hello,
>> The newer system should be as convenient as dll.sources model. Without as
>> easy step as to add just one line for new Foo.cs in Bar.dll.sources (or more
>> importantly for contribution, FooTest.cs in Bar_test.dll.sources), I'm not
>> likely enthusiastic to contribute new code.
> If all y
Hello,
> This is a good idea. We repeatedly get questions about "We are
> willing to pay for these bugs to be fixed" and only have a handful of
> contractors that we know that can help users.
In addition, the other question that we get repeatedly is regarding
training on Mono-specific APIs like
>> is there a list of people available to fix mono bugs for hire anywhere?
>> (A quick google search for commercial support mono only brings up
>> the novell offering, which seems to be tied to licensing the OS.)
This is a good idea. We repeatedly get questions about "We are
willing to pay for t
Hello,
> I noticed another issue: the project does not support tests. Test project
> will require NUnit addin (am not sure if it exists for 2010) and thus
> excludes Express users.
> But that should not mean that it's okay for Windows-based hackers to totally
> ignore those NUnit tests.
I could u
Hello,
> The newer system should be as convenient as dll.sources model. Without as
> easy step as to add just one line for new Foo.cs in Bar.dll.sources (or more
> importantly for contribution, FooTest.cs in Bar_test.dll.sources), I'm not
> likely enthusiastic to contribute new code.
If all you c
Hi,
I've made a little browser window according to this one:
http://huseyincakir.wordpress.com/2010/01/22/mono-webbrowser-with-webkit-gtk-not-winforms/
Furthermore, I got GTK# and Glade applications working on Windows.
My understanding is that I could also use the very same webkit-sharp.dll
on
My MSBuild.NUnit project, can be of help (See
https://github.com/monoman/MSBuild.NUnit ).
The main assumption is that you can add the reference to the task
assembly in msbuild proj file as an "implicit" reference to the
matching framework/runner assemblies (a parallel non-GAC
installation), so avoi
What exactly do you need fixed ?
If you're searching for an ultra-cheap, ultra-UNreliable solution for
outsourcing an ultra-work-insentive fix,
go to
www.rentacoder.com
Else, I'd be interested, but since I'm otherwise employed, my time is
very limited.
And what distro would you need it for (I'
Hello,
> project will require NUnit addin (am not sure if it exists for 2010) and
> thus excludes Express users.
You don't need nunit addin, you can use any internal or external tool
which can run nunit including nunit-console. The trouble is to build
with correct nunit framework version to be ab
+1 :-)
NUnit plugins for VS2010:
Visual Nunit 2010:
http://visualstudiogallery.msdn.microsoft.com/c8164c71-0836-4471-80ce-633383031099?SRC=VSIDE
TestDriven.Net:
http://visualstudiogallery.msdn.microsoft.com/3a1fdba7-eadd-4b35-84fd-ec3d559e657d?SRC=VSIDE
Continuous Testing for Visual Studio 2010:
h
I noticed another issue: the project does not support tests. Test
project will require NUnit addin (am not sure if it exists for 2010) and
thus excludes Express users.
But that should not mean that it's okay for Windows-based hackers to
totally ignore those NUnit tests.
It might be still possib
>> Ideally, we can turn this into building Mono entirely using
>> msbuild, which should be a lot faster than using the cygwin/makefile
>> setup.
Hooray! This is something that's been lacking for a long time.
Hopefully it will encourage debugging/testing/fixing on windows for
core team members a
The newer system should be as convenient as dll.sources model. Without
as easy step as to add just one line for new Foo.cs in Bar.dll.sources
(or more importantly for contribution, FooTest.cs in
Bar_test.dll.sources), I'm not likely enthusiastic to contribute new code.
So far *.dll.sources coul
22 matches
Mail list logo
