Thanking you Sir!Dr Herbie said:We used this for part of a new subsystem at the end of last year (rest of system used ADO.NET but we wanted to test alternatives).
In comparison to Entity Framework (EF), NHibernate is currently better; use of Plain Old C# Objects (POCO) is not possible in Entity Framework v1 (apparently being added in V2). Tooling of EF is better, but having to use auto-generated classes takes away some of the flexibility that NHibernate gives. ALthough there are tools to auto-generate NHibernate classes, they didn't seem up to much (or I couldn't get them to work), so we ended up coding them up by hand. Fluent NHibernate looks like a better way forward for this than the default XML files.
I plan to re-visit Entity Framework when V2 is released and see if it's an improvement.
Linq to NHibernate is still baking, but makes a good alternative to Linq to SQL (which is no longer supported, I believe).
I'm still an NHibernate novice, but if and when we get a new project, it will be given serious consideration.
You may want to try this http://blogs.msdn.com/wpfsdk/archive/2008/11/10/wpf-designer-hotfix-is-posted.aspxjenkis said:Zeo said:*snip*
This occurs regardless of the hardware (home / office) and also in multiple vpcs. The office machine is pretty much top spec, quad core, 3gb ram , xp. ...
Simple WPF projects run fine in all environments.
Let me summarise the events:
1. VS crashes when I build in the case where I have a xaml file open that includes merged dictionaries, or a file that references a StaticResource that comes from a file that has merged dictionaries. This is documented in the SP1 release notes as a known bug I am fairly sure.
2. As a result of 1, I have to remember to close almost all xaml files before building or a guaranteed crash happens. I can leave .cs files open.
3. I have broken down my styles in a hierarchy, eg brushes.xaml is referenced by textstyles.xaml is referenced by controlstyles.xaml / datatemplates.xaml / ....etc. Therefore everything falls into category 1, as then all my UI controls reference the StaticResources and templates for everything.
4. I have turned off the designer so as to open in full xaml view, but opening the xaml designer is very slow.
5. I am sure you can imagine the pain of having to remember to close files all the time, then having to wait to open each one again.
6. Independently of all that, even with all windows closed upon build, it freezes on average every 30 mins as the original author describes.
I am almost not joking when I suggest to myself that this crashing / recovery activity should be in the project plan. It costs me 15-30mins a day, if you throw in the loss of momentum as well.
Any suggestions would be appreciated.
Obviously Silverlight and WPF aren't new skills nor are Code Contracts, Linq to SQL etc.Turbodad said:
How secure do you feel as a developer if you have Silverlight and WPF skills, and businesses say they would rather use Open Office and Mono, because it is free, rather than paying you £60 000 a year?You learn new skills. (I cannot believe I had to tell you this.)
Has anybody used this ORM and is sufficiently pleased with it that they would recommend it over Linq to SQL or the Entity Framework?
I have read up about it on their website, but, as with these things, someone who has actually completed a project with it is usually the best person to seek advice from.
But surely open standards are giving even more away?blowdart said:What does the underlying cost of a system have to do with your salary? At the end of the day the system costs are minimal compared to development costs when you are developing a custom system. Of course if there are open source systems that are 95% of the way there then you have a problem ...
Personally I think having things compete equally is fine. But the requirement should be for open standards/file formats/data interchange rather than forcing open source.
It is a little discomforting working in a field where things are generally getting harder, and having the general public and Government devaluing Computer Science in announcement such as this. I recently looked at an old Citrix application that a contractor needed to get access certain modules of in order in order to improve their business processes. XML access would have been brilliant, as they would have just gotten the set of data they need, and built their processes around that - forget creating a web service, as nobody touches the database except the database owner. As it is, the symbiotic relationship can't and won't ever develop at a mentionable rate, because the contractor can say, your system is old and you won't allow me access to it, and the owner will say, that it is too expensive to allow access. Both are now locked into a relationship that does not really develop and is as static as you like, but they are still making profit.
I have come to the realisation that some companies say they strive for efficiency in principle, but even if they have a system that is decrepit and could use open standards to improve, they they will somehow defy logic, and shy away from sharing data.
No, it is not Deja Vu. In this post I was criticised by some for being factually incorrect, but it is now Official.
Is it really worth continuing to put all your eggs in one technological basket (or Company) as a developer, or is it about time one diversified, maybe worked in another field?
How secure do you feel as a developer if you have Silverlight and WPF skills, and businesses say they would rather use Open Office and Mono, because it is free, rather than paying you £60 000 a year?
Should Mono have ever been allowed to get its hand on Windows Forms?
Why develop Moonlight if companies (enterprises) are only going to turn their back on you, and use thin client applications in Firefox on Linux?
Starting a WPF application isn't too painful now, but it is not going to be as quick a previous. The real pain in visual studio is large projects and Websites that take an age to load at start-up and as long to build when debugging.CannotResolveSymbol said:Looks like VS2010 is going to be all WPF... screenshots available here: http://blogs.msdn.com/jasonz/archive/2009/02/20/a-new-look-for-visual-studio-2010.aspx
Pretty... but probably won't help performance or startup time one little bit.
I have been working with WPF quite a bit recently, and the data grid will never be as fast as the Windows Forms one - ever - but my is the WPF grid more customizable. The problem is that in your typical WPF application, if you look at all the namespaces needed just to get the thing to work compared with Windows Forms, the Libraries are dwarfed.
That VS 2010 will be slower is a given, but there will be recompense, and then some!
I anticipated that assertion, but am reliably informed that Microsoft change their UI dramatically and drastically when beta testing Office. Also, the image is not the from page in Office but the Calendar, but I agree with you it "looks" as if the ribbon has been used like Access, so Outlook is becoming a pure Single Document Interface (SDI), but this is all speculation!DCMonkey said:vesuvius said:*snip*
Look at the last of these leaked screenshots of Office 14:
Luckily, initially I installed Windows 7 onto an old hard drive, and have managed to hook it up now.Bas said:vesuvius said:*snip*
All fine, I'm just saying that there are plenty of intelligent people here on nine, and some of them actually like the taskbar. Saying that "the task bar is a case of the Emperors New Clothes" is basically saying that these people are gullible simpletons that'll immediately love anything Microsoft tells them is great.
If you don't like the new taskbar, fine. There's plenty I don't like about it either. But saying that the only reason people can possible like it is because they've been told to, rather than because of what they saw and experienced themselves? I don't know.
My Windows 7 task bar will be set to "Never Combine" as the image above shows. It is then possible to use the task bar in the traditional manner, but it negates all the hard work the windows team have done.
My disapprobation has been centred around the fact that suddenly when you are used to taking an escalator (to get to the first floor) in a building, you are told that you must take an elevator.
Sometimes, it is quicker to use one or the other (if going to the third floor for instance), not the impression given thus far by the Windows team, that you either use an elevator, or everything else is like using steps.
This is the lesson all proponents of the task bar must learn.
Even the most Gifted and Intelligent people make mistakes, take your recent UAC debacle.Bas said:vesuvius said:*snip*
That's a very dismissive attitude, if not simply an insult of the intelligence of some people here on C9.
I say what I think - and will stand by my errors in judgement, and openly admit to them - and certainly don't mean to insult the intelligence of some people here on nine. From luminaries like Larry Osterman, to PaoloM and BHpaddock, one is certainly privileged to have the opportunity to interact with people on the cutting room floor.
I do know however, that developing software is hard, whether at Microsoft or at a small start up, and Microsoft employees don't always have the correct answers or solutions, and my considerable experience supporting users in languages that pre-date C and applications made in those languages, gives me a certain confidence when I see features that are going to cause problems down the the line. I am a qualified C++ developer so don't really feel that there is magic going on in Windows, any more than an Air Traffic Control system written in C. This stuff is all hard and I give my respect to Microsoft and the folks at events like JAOO etc. Until the recent interest in concurrency, few people had heard of Haskell or functional programming. Look at MVC or the MVP patterns that are emerging, even the PEX video recently posted based on Bertrand Meyers Eiffel (design by contracts). This isn't all just Microsoft stuff, and you will find these people far more scathing compared with the misperceived insults I have not made.
I am not a betting man, but am willing to be you any amount of money you like, that unless changes are made, then there will be a backlash at the current task bar, and that a lot of people will opt to revert to the previous setup. This is because an attempt has been made to fix a problem that did not exist.