ahhh... the power of passive-aggressive words. maybe i change the term "thin client" into "weak client".
i'm upset by this because i really used cashback a good bit. saved me $100's.
at one point ebay was 35% cashback with paypal. looks like they're doing one last push though with some stores. betbuy right now is 20%, so you could get a nintendo wii for $120 (already on sale for $150).
i really hope they bing it back.
something like that bit me a while ago. it didn't throw an error and we ended up with 1000's of truncated survey records... i don't think it was a cell limitation though, rather a column limit.
upgrading wasn't an option for us so we had to get a bit creative, processing data in discrete blocks.
i've seen something similar before but i have not been able to duplicate it. it happens so rarely that i haven't investigated it too much. it usually manifests itself with a phone call once or twice a year.
them: the links on the page don't do anything
me: press f5
them: oh that did it, now they work. thank you.
i attribute it to "wonkiness" of the browser (very technical term). if it happened more, i'd probably have them view source and send me the html so i could verify that it looked okay. as always, your situation may be caused by something else, but i've had similar problems on paypal and other high visibility sites.
kettch said:itsnotabug said:*snip*
Why would talking abou jQuery get you into trouble? jQuery is now fully supported under ASP.NET 4 and VS2010. It's been blessed by The Gu.That should be enough for most people here.
wow! that's great news about jQuery (and an indictment of how behind-the-times i am).
i agree figuerres. some data-centric controls are invaluable... i was mostly talking about the controls that try to do *too much* like the menu and wizard. as soon as you require functionality/styling that's not offered out of the box, you're stuck trying to over-ride their rendering and at that point, you may have well just rolled your own solution < that's the only way to get the granular level of control.
i also love the multi-view. i think the wizard is derived from it, so if you need wizard-like functionality, the multi-view exposes a very useful event model to exploit.
as far as email goes, you can spend a lot of time trying to get your relay rules set with your stmp server but if you have access to the virtual stmp that comes with windows server you can send emails with something like this:
//create the mail message
MailMessage mail = new MailMessage();
//set the content
mail.Subject = "Hello.";
mail.Body = "<b>Wow, this is easy!</b>.";
mail.IsBodyHtml = true;
SmtpClient smtp = new SmtpClient("127.0.0.1");
you can even write the email files directly to the transport folders, bypassing the network layer completely. check this resource for email guidance: http://www.systemnetmail.com/
can you post your code?
i had problems with the clipboard before but worked around it by using word interop + doc.append. it required an additional save of a temp word doc that only held the image. not ideal but it got it off my plate (may not work in your situation).
my humble opinions/observations (you may find them completely wrong in your application):
1) use jQuery for all client side. forget the built-in controls. this won't win me many friends around here
2) see 1
3) depends. i like session state for smaller sites, 3rd party? yes and yes (post and querystrings)
4) if possible use the virtual smtp server on the iis box
5) what about multi-views?
6) i like datagrids but you have to tweak it (look at the ondatabound event), but it really depends on your context
7) ummm. in terms of updating (like a cms)? or just not using static text? ALWAYS
8) cuz microsoft likes to keep things easy (not really but the opposite is true also, things work in firefox... not so in ie)
Vs. bat files, it provides a much richer API. A lot of things that can barely be achieved with a bat file by an expert can be trivially implemented in a PowerShell script.
Vs. VBA scripts, it provides an imediate mode, or shell. Comparing PS to these two isn't as "apples to apples" as comparing it to BASH/CSH/etc (comparing it to BAT I suppose is comparing it to CMD which is "apples to apples", but CMD isn't in the same league as the others).
Other noteworthy reasons why PS is worth learning:
1. It can fully utilize .NET libraries. This means there's very little you can't accomplish within PS rather easily, whereas in batch files you'd be SOL and in VBA you'd often be stuck looking for a COM component.
2. It works with object streams rather than text streams, which is much less fragile and a lot more powerful.
3. Many enterprise systems, such as Exchange, are moving towards PS management interfaces rather than COM interfaces. IOW, it's getting to be more and more difficult to manage these systems using BAT and VBA scripts.
4. The shell is a much nicer command line environment in comparison to CMD. Live in it for a while and you'll never go back to CMD.
5. PS provides a very powerful command line parsing infrastructure and help system, usable from your own scripts. This vastly improves the quality of your scripts with little effort.
If I thought about it some more, I could come up with other reasons. PS is a game changer. It's got its own set of problems, some of them quite annoying, but overall it's the best shell and scripting environment I've ever used.
hmmm... number 3 will probably be my reason to get into it if any.
i guess i've been doing it "wrong" by just writing little console apps (full .net api, full flexibility, error logging) and kicking them off via cmd with arguments, sql job or scheduler.