Comments
Sort by recent activity
Do you still have the zip I sent you previously? 'tis in there. / comments
Do you still have the zip I sent you previously? 'tis in there.
That's fine; for insane code, simply reporting an error (rather than killing VSTS) seems reasonable. And yes: that generated code is pure evil, but great for test purposes ;-p / comments
That's fine; for insane code, simply reporting an error (rather than killing VSTS) seems reasonable. And yes: that generated code is pure evil, but great for test purposes ;-p
dll + project sent by e-mail / comments
dll + project sent by e-mail
Cheers. / comments
Cheers.
Much better now; thanks. There is still an unpredictable-length delay at the end of each assembly, but it is much easier to see how long it might take now. / comments
Much better now; thanks. There is still an unpredictable-length delay at the end of each assembly, but it is much easier to see how long it might take now.
mihies wrote:
I agree with Alex and don't have really and need for more clutter :-)
I really think a progress update would be hugely valuable. Since it does assemblies in parallel, why not "In progress (17%)" in the "Status" column (obviously, replace 17 with the current progress...).
Setting expectation is important. / comments
mihies wrote:
I agree with Alex and don't have really and need for more clutter :-)
I really think a progress update would be hugely valuable. Since it does assemblies in parallel, why not "In ...
Indeed; and that is how object explorer (the inbuilt one) already works if you drag on object from the tree. There may be other object explorer functionality that is useful to people - the properties window perhaps (guessing). / comments
Indeed; and that is how object explorer (the inbuilt one) already works if you drag on object from the tree. There may be other object explorer functionality that is useful to people - the properti...