[MonoDevelop] Trace/Debug output in MonoDevelop

[Mike Christensen]

Yea, I see a lot of people gripe about the WebForms designers and all
that stuff.  I couldn't give a rat's ass if that works, but I'm sure
it's a deal-breaker to certain people :)

I just want like VS2005 feature parity and I'd be set heh..

On Sat, Oct 30, 2010 at 10:29 AM, Charlie Poole <charlie at nunit.com> wrote:
> Hi Mike,
>
> I see I inadvertently took us off-list, so I'll put us back on it.
>
> That's a good point. And also an illustration of what I'm getting at.
> Not being a web developer gives me an entirely different perspective
> on what's important.
>
> In the past, I've given out general advice on when/whether to switch,
> but I think I'll stop doing that - it's really project dependent.
>
> Charlie
>
> On Sat, Oct 30, 2010 at 10:16 AM, Mike Christensen <mike at kitchenpc.com> wrote:
>> I'm very very close to pulling the trigger to port to Mono and Linux
>> servers, maybe 3.0 will do it for me.  I think with the new garbage
>> collector, the runtime is probably pretty dang good now..  Perf I'm a
>> bit worried about, since part of my app is extremely perf critical.
>> MonoDevelop I think is still a ways off, maybe another version or
>> two..  The thing that I will miss the most about Visual Studio is the
>> integrated script debugger.  It simply blows away anything else out
>> there for debugging Javascript.  Now if MonoDevelop had /that/, I'd be
>> completely sold..  I think it's on the to-do list, but who knows if
>> someone will pick up that work item.  I think it would mean
>> integrating MonoDevelop in with WebKit.
>>
>> Mike
>>
>> On Sat, Oct 30, 2010 at 9:48 AM, Charlie Poole <charlie at nunit.com> wrote:
>>> That's a good point... not so much about the immediate window, which I
>>> don't use, but about the need to focus on the specific features one makes
>>> use of when deciding if it's time to convert.
>>>
>>> For example, I couldn't use 2.2 because of issues with linked files, something
>>> that might not matter in some projects. With 2.4, it works - albeit with a few
>>> glitches - so I was able to start using MonoDevelop for my Linux builds.
>>>
>>> At this point, the level of glitches in MonoDevelop is sufficiently low (for me)
>>> that it's easier to use it than to build in Windows, move the assemblies to
>>> Linux, run tests there, etc.
>>>
>>> It's all relative.
>>>
>>> Charlie
>>>
>>> On Sat, Oct 30, 2010 at 4:19 AM, Mike Christensen <mike at kitchenpc.com> wrote:
>>>> I think the day that the Immediate Window really works well is the day
>>>> I would switch.  I use the heck out of that feature in VS..  It's
>>>> definitely making progress though, that's for sure..
>>>>
>>>> On Sat, Oct 30, 2010 at 4:01 AM, kuseman <marcus at in-process.se> wrote:
>>>>>
>>>>> @quandary: You should get a prize for the most constructive post on this
>>>>> mailing list :)
>>>>> --
>>>>> View this message in context: http://mono.1490590.n4.nabble.com/Trace-Debug-output-in-MonoDevelop-tp3016495p3020182.html
>>>>> Sent from the Mono - MonoDevelop IDE mailing list archive at Nabble.com.
>>>>> _______________________________________________
>>>>> Monodevelop-list mailing list
>>>>> Monodevelop-list at lists.ximian.com
>>>>> http://lists.ximian.com/mailman/listinfo/monodevelop-list
>>>>>
>>>> _______________________________________________
>>>> Monodevelop-list mailing list
>>>> Monodevelop-list at lists.ximian.com
>>>> http://lists.ximian.com/mailman/listinfo/monodevelop-list
>>>>
>>>
>>
> _______________________________________________
> Monodevelop-list mailing list
> Monodevelop-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/monodevelop-list
>