you should have bought a laptop! No need to ship it, just carry it along on the plane. Plus, you can take it with you to class. Not very helpful now, I know, but maybe it will make someone else think about getting a laptop for school instead of a desktop system.
I didn't buy mine at Wal-mart, so I think I am safe. Wow, I can't believe they did that! I wonder what the motivation was. I suppose it forces you to go back to Wal-mart to get it filled or something?
If M$ wants to sell/make money in S. Africa, assuming this good idea becomes law, then they are free to do so as long as they don't arbitrarily violate basic, broadly agreed upon standards
From what I read, it sounds more like if MS wants to sell products to the South African government they have to pay this 10% fine. So, they can continue to sell products to everyone else in South Africa without paying this fine. I think this is pretty much the same as saying "we will not buy products from MS until they comply with open standards".
Re:I don't think Fossil did their homework...
on
Palm OS Wristwatch
·
· Score: 1
I agree with you and would add that in the past when I had taken math tests, if you showed your work on the paper and got something wrong because you messed up doing some basic stuff like carrying the 1, the instructor would give you partial credit if you did everything else right (or sometimes even full credit).
Are you sure they are Walmart only threads? I know there were some changes to the standard fittings on propane tanks recently (when I say recently I mean in the last few years). At least that is the case with the small tanks for use with grills (what are those, 15 lb. tanks?). I don't have any references on it, but the old fittings required a crescent wrench to un-screw and the new ones have a different fitting that allows a hand-tightened hose. The old hoses still work too, I didn't have to change the hose on my grill when I bought a new tank.
Re:Do you realise what you've said?
on
Hijacking .NET
·
· Score: 1
Anyways, OpenZaurus is so far ahead of the Sharp rom that I won't even bother with this new version.
This update is really nothing like the older Sharp ROMs. It is much better. It doesn't run everything as root anymore either. The support for network profiles is a lot better too. Now I can set up a separate profile for WiFi at work and at home, each with separate keys. That alone was worth the upgrade! You should give it a try. You don't have control over how much RAM to dedicate to storage like on OZ, but it really is a nice upgrade from the 2.37 or 2.38 Sharp ROMs.
If you have a Zaurus SL-5500, take a look at the new 3.10 ROM for it from Sharp. It has the new software from the SL-5600 and is much better than the 2.37 or 2.38 versions were.
He's been pretty helpful whenever we have needed it. It's all been through email. I would guess that he may not have the time to monitor the newsgroups all the time. He has a "day job". If you build your app against the lowest version of Outlook you want to be compatable with, it should also work with later versions. We build our product against Outlook 2K and it works with 2K, XP and 2003 Beta. As for performance, I am not doing a lot of stuff at one time, so maybe I just don't notice it. Most of our Outlook integration is popping up pre-formatted email messages. We also do some syncing of Tasks and Appointments, but usually not a very high volume.
Since Redemption is COM, you can use it from C# (or any.Net language) by using COM Interop. If you are using Visual Studio.Net, it is as simple as adding a reference to the "SafeOutlook Library" to your project. Otherwise you need to use the tlbimp.exe utility to do it.
As for memory leaks, I'm not sure about that. You do need to cleanup after Outlook and Redemption very well though. When I first started using it in.Net, I was sloppy because I was used to the CLR cleaning up objects after they go out of scope. If you don't clean up well, you can end up with a background OUTLOOK.EXE process running. Make sure to create an instance of the MAPIUtils object and execute the Cleanup() method, and of course set everything to null.
Performance doesn't seem to be much worse than accessing the Outlook object model directly. I did run across very poor performance accessing a list of Contacts, I was iterating through the Items property of a MAPIFolder. Dmitry (author of Outlook Redemption) gave me some help to access them a different way and it was MUCH faster. If I remember correctly I was trying to get about 200 Contacts and it was taking a minute or 2. The method he showed me ended up taking a few seconds. What you end up doing is creating a MAPITable and setting its Item property to the Items property of a folder. Apparently accessing the MAPITable is much faster than going through the Folder.
Something else I ran up against when creating an addin for Outlook in C# was that when Visual Studio.Net generates the Outlook interop dll, it sets all the events to private. So, in order to respond to any events in Outlook, you have to use ildasm.exe to disassemble the assembly and manually go through and mark them public, then use ilasm.exe to regenerate the binary. Kind of a pain in the ass, but once you do it, you don't have to do it again. Unless VS.Net regenerates the Interop assembly for you again;)
Now, I'll admit that.Net-->COM-->Extended MAPI isn't the most elegant solution to the problem. If I were a C++ developer I would have written my own Extended MAPI access classes and made them accessible in a native.Net assembly. However, it has been a lifesaver for the project I am working on. It would be really nice if Microsoft made a way to have trusted components that can access Outlook directly. I have heard something about this maybe in Outlook 2003, but haven't read anything defining how it is done, or if it can be done.
It would be very easy to tell if the COM object was passing email addresses back to the "mothership", just do some traffic sniffing, that's simple. Besides, how many of us actually read every line of source code for the open source apps that we use? Not many I would bet.
Redemption is not written in VB it is written in C++ (not that it really matters). I haven't had any real problems with it. Most of the people I have run across trying to write addins for Outlook or apps to interact with it were frankly, not up to the task as far as skills go. I think that may be why one would see so many problems with it in the addins newsgroups.
I know the company that he works for and he was recommended to us as an Outlook/MAPI guru by the former CEO of said company. So, that's good enough for me. I realize that doesn't do anything for anyone else, so do whatever you think is correct.
There is another way! Use Outlook Redemption. This COM object does all the Extended MAPI stuff for you and is very easy to use. I have used it from VB 6 and also C#. This guy also has another tool on his site called Outlook Spy which is pretty handy.
My suggestion to MSFT.... release VS 7.0 or risk a crippled developer community. Any would-be Borlands, feel free to be the king of the market because MSFT won't release VS 7.0 (without the.net support) until hell freezes over.
Visual Studio.NET is basically Visual Studio 7. You can still build MFC C++ apps with no need for the.NET Framework on a client PC. (Maybe you already know this, but others may not...)
It should be. I don't see any reason to proliferate more COM into the world. We still need to interoperate with COM, but I hope no one is building new COM based apps!
Will ALL Windows programming be done with.NET?
Was all Windows development done with COM in the past? No, so why would ALL new Windows development be done in.Net?
Will games be developed with.NET? If games aren't developed with.NET and Microsoft is killing COM, then what future for games development on Windows?
Was COM really all that usefull for game programming in the first place? I doubt the death of COM will make much difference to most game developers.
Slashdot Mirror
you should have bought a laptop! No need to ship it, just carry it along on the plane. Plus, you can take it with you to class. Not very helpful now, I know, but maybe it will make someone else think about getting a laptop for school instead of a desktop system.
What is your GPL application?
I didn't buy mine at Wal-mart, so I think I am safe. Wow, I can't believe they did that! I wonder what the motivation was. I suppose it forces you to go back to Wal-mart to get it filled or something?
From what I read, it sounds more like if MS wants to sell products to the South African government they have to pay this 10% fine. So, they can continue to sell products to everyone else in South Africa without paying this fine. I think this is pretty much the same as saying "we will not buy products from MS until they comply with open standards".
I agree with you and would add that in the past when I had taken math tests, if you showed your work on the paper and got something wrong because you messed up doing some basic stuff like carrying the 1, the instructor would give you partial credit if you did everything else right (or sometimes even full credit).
Are you sure they are Walmart only threads? I know there were some changes to the standard fittings on propane tanks recently (when I say recently I mean in the last few years). At least that is the case with the small tanks for use with grills (what are those, 15 lb. tanks?). I don't have any references on it, but the old fittings required a crescent wrench to un-screw and the new ones have a different fitting that allows a hand-tightened hose. The old hoses still work too, I didn't have to change the hose on my grill when I bought a new tank.
I hate it when my "priverlages" get elevated.
I guess that's why they have Perl.Net and Managed Extensions for C++, huh?
PerlNet
This update is really nothing like the older Sharp ROMs. It is much better. It doesn't run everything as root anymore either. The support for network profiles is a lot better too. Now I can set up a separate profile for WiFi at work and at home, each with separate keys. That alone was worth the upgrade! You should give it a try. You don't have control over how much RAM to dedicate to storage like on OZ, but it really is a nice upgrade from the 2.37 or 2.38 Sharp ROMs.
Maybe it will make your Z more useful to you?
He's been pretty helpful whenever we have needed it. It's all been through email. I would guess that he may not have the time to monitor the newsgroups all the time. He has a "day job". If you build your app against the lowest version of Outlook you want to be compatable with, it should also work with later versions. We build our product against Outlook 2K and it works with 2K, XP and 2003 Beta. As for performance, I am not doing a lot of stuff at one time, so maybe I just don't notice it. Most of our Outlook integration is popping up pre-formatted email messages. We also do some syncing of Tasks and Appointments, but usually not a very high volume.
As for memory leaks, I'm not sure about that. You do need to cleanup after Outlook and Redemption very well though. When I first started using it in .Net, I was sloppy because I was used to the CLR cleaning up objects after they go out of scope. If you don't clean up well, you can end up with a background OUTLOOK.EXE process running. Make sure to create an instance of the MAPIUtils object and execute the Cleanup() method, and of course set everything to null.
Performance doesn't seem to be much worse than accessing the Outlook object model directly. I did run across very poor performance accessing a list of Contacts, I was iterating through the Items property of a MAPIFolder. Dmitry (author of Outlook Redemption) gave me some help to access them a different way and it was MUCH faster. If I remember correctly I was trying to get about 200 Contacts and it was taking a minute or 2. The method he showed me ended up taking a few seconds. What you end up doing is creating a MAPITable and setting its Item property to the Items property of a folder. Apparently accessing the MAPITable is much faster than going through the Folder.
Something else I ran up against when creating an addin for Outlook in C# was that when Visual Studio .Net generates the Outlook interop dll, it sets all the events to private. So, in order to respond to any events in Outlook, you have to use ildasm.exe to disassemble the assembly and manually go through and mark them public, then use ilasm.exe to regenerate the binary. Kind of a pain in the ass, but once you do it, you don't have to do it again. Unless VS.Net regenerates the Interop assembly for you again ;)
Now, I'll admit that .Net-->COM-->Extended MAPI isn't the most elegant solution to the problem. If I were a C++ developer I would have written my own Extended MAPI access classes and made them accessible in a native .Net assembly. However, it has been a lifesaver for the project I am working on. It would be really nice if Microsoft made a way to have trusted components that can access Outlook directly. I have heard something about this maybe in Outlook 2003, but haven't read anything defining how it is done, or if it can be done.
Redemption is not written in VB it is written in C++ (not that it really matters). I haven't had any real problems with it. Most of the people I have run across trying to write addins for Outlook or apps to interact with it were frankly, not up to the task as far as skills go. I think that may be why one would see so many problems with it in the addins newsgroups.
I know the company that he works for and he was recommended to us as an Outlook/MAPI guru by the former CEO of said company. So, that's good enough for me. I realize that doesn't do anything for anyone else, so do whatever you think is correct.
There is another way! Use Outlook Redemption. This COM object does all the Extended MAPI stuff for you and is very easy to use. I have used it from VB 6 and also C#. This guy also has another tool on his site called Outlook Spy which is pretty handy.
I haven't looked at DirectX in a while. Didn't it used to be standard (non-COM) libraries?
Maybe, but you can also just download it here: http://www.chsoft.com/dv.html
By the way, that was the first link that came up on Google when I searched for "desqview".
There must be some sort of market for these old cartridges, otherwise there wouldn't be an archive of them to download from in the first place.
Visual Studio .NET is basically Visual Studio 7. You can still build MFC C++ apps with no need for the .NET Framework on a client PC. (Maybe you already know this, but others may not...)
It should be. I don't see any reason to proliferate more COM into the world. We still need to interoperate with COM, but I hope no one is building new COM based apps!
Will ALL Windows programming be done with .NET?
Was all Windows development done with COM in the past? No, so why would ALL new Windows development be done in .Net?
Will games be developed with .NET? If games aren't developed with .NET and Microsoft is killing COM, then what future for games development on Windows?
Was COM really all that usefull for game programming in the first place? I doubt the death of COM will make much difference to most game developers.
Can you explain what you mean by this? It's not a troll, I am genuinely interested in what you mean.
And this is news because???? The article on MSDN was posted in July of 2002! Is there something new about Rotor on BSD that I am missing?
Looks like what's a bit late?
The really sad thing is that Ford hasn't learned a thing from this. They are still building cars that catch fire when struck from behind.
And here: DotGNU
Everybody makes spelling mistakes, but it is pretty funny considering the topic of your post!