Pete_Brown
-
. @ the programmer who wrote that Windows API told me it was not available via IDispatch. I tend to trust him :)
about 2 hours ago
from TweetDeck
-
$35 well spent. Emicsoft AVCHD converter converts from MTS to AVI, lossless. Was hating the camera software, and all others were lossy.
about 2 hours ago
from TweetDeck
-
Would you like to play a game?
about 2 hours ago
from TweetDeck
-
. @ it needs more than that. It needs better networking / identity access, more local APIs, access to full client FX.
about 2 hours ago
from TweetDeck
-
. @ regardless of the future of WPF /SL, COM is not the long-term answer. Too messy unless you're accessing stuff already there.
about 3 hours ago
from TweetDeck
-
. @ but not necessarily an IDispatch-compatible driver. For example, sensor API is not accessible via IDispatch. Needs a wrapper.
about 3 hours ago
from TweetDeck
-
. @ If I had used WPF, no COM DLL required, just good old desktop .NET. COM is a great enhancement, but not the end-game
about 3 hours ago
from TweetDeck
-
. @ so, great for office automation and similar scenarios. For the sensors, I had to create and register local COM dll. ugly.
about 3 hours ago
from TweetDeck
-
. @ Dude, have you tried the COM API in Silverlight? Sweet, but only if the COM servers are already installed and are IDispatch
about 3 hours ago
from TweetDeck
-
@ also, number-wise you have to count the actual evangelists like Jaime and Tim Sneath. I'm a content/community guy :)
about 3 hours ago
from TweetDeck
in reply to JustinAngel
-
. @ I'll put up a post showing how I accessed the sensor API from Silverlight 4. Very neat, but not a pretty client-side install.
about 3 hours ago
from TweetDeck
-
. @ always need to be something that can access all that Windows provides, and SL is not currently there [2/2]
about 3 hours ago
from TweetDeck
-
. @ that said fore sure the gap is closing. Will they merge or something in the future? Hard to say, but there will always [1/2]
about 3 hours ago
from TweetDeck
-
. @ COM is useful, but it doesn't get you as much access as you think, and not as easily. Plus, VS10, Blend are major WPF apps.
about 3 hours ago
from TweetDeck
-
@ and don't judge by numbers. There will be only one ASP.NET community PM, that's no comment on future of ASP.NET :)
about 3 hours ago
from TweetDeck
in reply to JustinAngel
-
@ @ and, FWIW, my focus isn't WPF, It's "Windows Client Dev". I'm happy if people use SL, WPF, C++, whatever :)
about 3 hours ago
from TweetDeck
-
@ @ what I'm saying is SL isn't there yet. There are still many apps for which SL can't replace WPF.
about 3 hours ago
from TweetDeck
-
@ Silverlight may eventually get there, but for now and several years out, WPF still has a huge leg up for Windows apps.
about 3 hours ago
from TweetDeck
in reply to JustinAngel
-
@ I did some COM work in SL4 for the emulator. It's COM -- good for some things, but messy for others. Plus, IDispatch only.
about 3 hours ago
from TweetDeck
in reply to JustinAngel
-
@ @ to be fair, Silverlight adds x-plat and a simpler install model. WPF is where it's at for windows dev, though
about 3 hours ago
from TweetDeck
in reply to paulstovell
|
- Name Pete Brown
- Location Anne Arundel County, Maryland
- Web http://www.irrita...
- Bio Microsoft Dev Community Program Manager for Windows Client (WPF, SL, native, etc.), Father of two, Woodworker, Author, Aquarist, Former Silverlight MVP & INETA
|
