I’ve been pushing Atlas at work to my boss, and even wrote portal just to show how cool it was. Well , I'm not sure what to do after this beta 1 release. It seems MS has changed rules during the game. PageMethods don't work. Controlstoolkit is... I even don't what to look into... I don't know. I should have been smarter and kept quiet about Atlas.
Shame on you Atlas team.
It's 4:00 AM and I’m going to bed. Tomorrow I’ll say sorry to my boss and move my app to SAP.
What a waste of time.
-A
Shame on you Atlas team? Are you familiar with acronyms? Are you familiar with Microsoft's CTP acronym? It stands for Community Technology Preview. You were implementing a CTP techology when you were implementing Atlas into your system. The risk you take with that is having to update your application with the changes once the technology has been improved (which it definitely has been in this case). Shame on you for pointing fingers at Microsoft's Atlas team when really you're the ONLY one to blame. Next time take five minutes of your precious time (I don't care if it is 4:00am) and search the forums for an answer to your problem because there was one posted before you submitted this infuriating trash.
- Chris
I’m all familiar with these words.
Also I familiar with words as: compatibility, and consistency, and before I wrote my post, I read other posts on this website and other blogs. Not one post offered solution toPageMethods problem, and if you search this forum,you’ll find many angry developers and not one will tell they liked what MS done with this beta.
If this framework was made available to us, with all this videos and tutorials (advertisement), at least MS should keep it consistent.
Yea, one more thing .
I’ve been pro (support) MS since day one.
I like almost every product they released, and I’ve worked with beta products too, but this been so far biggest disappointment for me.
For the rest of you, be very careful when you use this product in your projects at work. You might loose your job.
-A
I am as dissapointed as the rest with the changes from Atlas to the new Beta...
Why? I had to change my perception of thinking and the way I was providing a solution...
Guess what: When you deal with Beta - pre-release - you expect that and understand there are a team of developers that are working to provide 'solutions'. Granted they may not be what 'we expect' from what we 'are accustomed to' but BETA, Alpha, pre-release etc.. being an early adopter means that there is more to the community than just youself. One aspect I sympathise with the Asp.Net Team is that they deall with thousands of us - all wanting one thing or the other all for different reasons. Those of us trying to embrace new technology have to realize its BETA, ALPHA, CARLIE, ZEBRA or whatever.. until its a RTM - then what have you may...
The one thing about Scott Guthrie's Team is they ARE on the forefront. They didn't wait until MagicAjax, or other suddenly had marketshare... instead they have been almost rogue like in the Microsft enviroment in bucking the trends and reacting to developers needs... You can *** to no end about how pre betas change what the current Beta's entail-- however you would be hardpressed to excuse them as not trying. It is very hard on the business side to provide the best in features withou sacrificing other customers.. it a given... but in actual true fashion - they provide documentation.. examples.. blog posts from real experts... and do actually respond to and devlope against customer feedback. We may not see it al the time and most of us do not have the ability to pop up a laptop in each of their office to demonstrate a problem... Look at the bigger pictiure... constructive critism is great... tell al of us (the devs using the techonology and those at MSFT programming it) what your issues are.. but slamming for the mere aspect that code from July qand the Beta release breaks... gimme me a break... Its great to have opinions but unless you desire to part of the solution - we all are part of the
problem... I find great resentment in your post merely becuase its so - uggh single minded...You took the same risks as we all did and each of us has the ability to influence the outcome in a POSITIVE MANNER...Try to get this level of product support for something BETA from IBM , Oracle or the likes...
They listen - and due to volume may not be able to respond to all of us (and believe me I which they would to my concerns)but none the less this is a 'community forum'...
Lets just say we ecided to take whatever pill we decided.. but until somthing is actually released as 'productiion' ready... its all BETA and the only thing we can do is positively outline what our needs and concerns are...
hello
kdpo:
I’ve been pushing Atlas at work to my boss, and even wrote portal just to show how cool it was. Well , I'm not sure what to do after this beta 1 release. It seems MS has changed rules during the game. PageMethods don't work. Controlstoolkit is... I even don't what to look into... I don't know. I should have been smarter and kept quiet about Atlas.
Shame on you Atlas team.
It's 4:00 AM and I’m going to bed. Tomorrow I’ll say sorry to my boss and move my app to SAP.
What a waste of time.
-A
yes, it's true: there are no more page methods, at least instance ones. I've already spend half a day trying to explain why we are better off without them, but it still seems like there are lots of guys using it. I must say that i never thought that so many people were using instance page methods...and, as I already saidhere, I don't really think there's any justification for using them since the penalty you pay is to high and I still haven't found any good justification for using those methods.
make no mistake about it: in the previous i'm saying that instance page methods should be back because it seems like there are lots of guys which depend on it. To me, this dependency still means lack of knowlegder in javascript or will to write some javascript code and use a web method or a static method to do the same work.
I mean, most guys just forget that AJAX means writing javascript and went straight away to page methods without even thinking in the consequences of those actions...
The real "shames" of the new pagemethod are
:
- Lack of support of the old method, both would be nice. (However the new one is better for me...)
- The annoying codebehind bug.
Check the descriptionhere, it's missing from the whitepaper.
hello.
i know that...and as i said, maybe there's space for both. in my opinion, no serious ajax page should use the old instance page methods...
Have to say I agree with others on this thread who are making the point that this isPre-Release software.
By all means look at it to get afeelfor where Microsoftmight be going with AJAX but I certainly wouldn't stake my job on it until it's gone RTM.
I for one think that the community involvement in this project is very valuable and worthwhile and will result in a much better end product than if MS had worked on this behind closed doors and only released it when it went RTM.
Migrating my app from July CTP to the new beta is requiring a lot of work, I assume it since it is prerelease software. But in my opinion, the really bad thing is: the beta has more bugs than the July CTP. I expected much more quality from this beta. I wonder why the ajax team guys have named it beta, I think they should just called it CTP.
Betaused to mean that a product was not to be used in production and was only being tested. Nowadays the rules have changed as Betas are made public and are in production. For example, Gmail is still marked as Beta but everyone uses it and it works pretty well. There are many examples of beta products being in production. The effect of this, unfortunately, is that the term beta has lost its meaning.
Because MSFT encourages developers to adopt pre-release products - it gives them some responsibility to make the products somewhat stable. My frustration is not the changes in the product but the bugs. Its not really usable.
Migrating my app from July CTP to the new beta is requiring a lot of work, I assume it since it is prerelease software. But in my opinion, the really bad thing is: the beta has more bugs than the July CTP. I expected much more quality from this beta. I wonder why the ajax team guys have named it beta, I think they should just called it CTP.
are you sure about this? i think this is not correct, specially if you concentrate on the core bits...
i think the main problem people are facing is that this beta is a complete new product which reuses several ideas of the ctp. so, it's as if we had to learn everything from the begining again. however, it's not fair to say that this release is worst that the previous one.
Because MSFT encourages developers to adopt pre-release products - it gives them some responsibility to make the products somewhat stable. My frustration is not the changes in the product but the bugs. Its not really usable.
hello.
i'm sure there are bugs, but it would help us all if we got a list (lke the one garbin developed) where everyone could put the bugs. btw, i've already seen 2 posts saying that this release has more bugs, but i see no one giving info on thebugs and on how to reproduce them.
[quote user="Luis Abreu] i'm sure there are bugs, but it would help us all if we got a list (lke the one garbin developed) where everyone could put the bugs. btw, i've already seen 2 posts saying that this release has more bugs, but i see no one giving info on thebugs and on how to reproduce them.
[/quote user="Luid Abreu]
bug description, repro, wokaround, and fix:
http://forums.asp.net/thread/1437484.aspx
[quote="Luis Abreu"] but i see no one giving info on thebugs and on how to reproduce them. [/quote="Luis Abreu"]
Bug description, repro and workaround:
http://forums.asp.net/thread/1440876.aspx
No comments:
Post a Comment