If you happen to have Exchange Server in the loop, beware the "Exchange Server RPC channel limit". This one bit me :-/amankazi said:Greetings,Kryptos said:*snip*
I have Office 2007 on Vista.
I am writing a application to read the outlook mail when user drag's and drop's a mail onto the Windows form(Same has to be achieved in Web application to. For this I am trying to create an UserControl and then add to the webpage). It is working fine with Office 2003. The problem is after adding the COM library "Microsoft Office 12.0 Object Library"
I am not getting the desired namespace "Microsoft.Office.Interop.Outlook" only "Microsoft.Office.Core" is available. Do I need to added some other dll? Even do suggest if there is other option to achieve the functionality expected.
Re: "in the street a lot of guys like me need a one man version of TeamSystem"figuerres said:Charles said:*snip*
also in some ways I like the term used by (forget his name but he is well known) he called ORM the "Viet Nam of software"
I will say that tools that try to build code often go that way, it's a tough war with nasty issues.
take the web service software factory that MSFT has published, I found that it does some things very well but has so many warts that it's not really ready for general use. I recall during the pre-launch wave for VS 2005 there was a lot of talk about software factories and new tools to build parts of the system.
so far i have not seen any huge sweeping advances in modeling that generates code.
sure we got the linq-to-sql gen but that is now officialy a dead end per MSFT edict.
I am not all negative here, please understand that I *KNOW* this stuff really truely starts to be "Rocket Science" to build the AI to understand a DB design and the client server / n-tier MVC / MVVM / whatever layers and so on.
just that the tools have a long way to go.
as you said: it's the eng. guys who have to communicate back to sales and marketing types.
that's the nut to crack....
not as hard when you have a setup like MSFT
hate to say this Charles but in the street a lot of guys like me need a one man version of TeamSystem!
that's right -- I need a cut down one man TS to help me do what the big teams do but on the scale of one guy doing almost all the roles.
I have to:
get the request
architecht the design / or chnages
work out the plan for how to do it.
write the code
update the server
update the client
check for bugs
tell the boss where it's at and how long.
keep track of the chnages.
make some graphcs when needed
and anything else ...
so which SKU of Team system is the right one? all of them.
but I do not have 5 guys to farm the work out to nor the time to run a server
and it's hard to get a spare server to run TFS on and keep it working ....
and the thing is the small shops like the one i work at often get lots of work but never get the big budget.
so I have like 6 servers i manage, 30 CE handhelds, 60 desktops and about 4 customers.
we mostly keep all that going with 2 staff, me and the CEO of our company.
I would love to be able to spend more time planning and stuff... but no one wants to pay for that, they want to have things done today.
So I do what I can....
I hear you figuerres. I'll add too that even small teams (5-30) which which I've been associated find too many barriers to adoption:
- Which SKU fits, how does it fit within our existing MSDN subscriptions, and what will it cost? One CA, USA governmental organization with which I was associated could not even get a (timely) answer from their MS vendor.
- Can't sell it to the keepers of the purse strings - REALLY this IS going to help us build better, more maintainable software faster. Trust me. Sadly, It seems it's always easier to drip, drip time and money into a hodgepodge of tools and cobble them together into a process that *seems* to work mostly OK.
Apr 06, 2009 at 3:15 PM
Ditto...Ray7 said:figuerres said:*snip*
Looks like a non-English news site that was run through Google Translator and then posted here without even reading it first.
net use /d d:Harlequin said:Matthew van Eerde said:*snip*
"Microsoft Windows Network: Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again."
Killing the D: drive already mapped seems to do the trick. Is there a line of code I can add before my NET USE to unmap the D: drive? Or will that /persistent trigger help this as well?
"If it's worth doing, it's worth doing right."joechung said:Bass said:*snip*
Oh so true - IMHO.
"...hard to convince people who have no clue how code works that it takes time and effort to do right."
Oh so very very true. But, alas, we must - IMHO.
Of course you'll then either have your username/password stored in plain text or, you'll have to type it in each time.ZippyV said:Harlequin said:*snip*
....still... easier than mapping manually each time.