tag:blogger.com,1999:blog-737100980526652029.comments2023-10-08T02:02:45.730-07:00Marcel van Eijkel's blog (Ing. / B ICT)Marcel van Eijkelhttp://www.blogger.com/profile/13020976692117196364noreply@blogger.comBlogger15125tag:blogger.com,1999:blog-737100980526652029.post-16026457847426064632010-04-08T06:15:17.849-07:002010-04-08T06:15:17.849-07:00hey
just signed up and wanted to say hello whil...hey <br /><br /><br />just signed up and wanted to say hello while I read through the posts<br /><br /><br />hopefully this is just what im looking for looks like i have a lot to read.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-737100980526652029.post-92166257923927449882009-09-09T07:08:48.152-07:002009-09-09T07:08:48.152-07:00I've been having this problem as well, althoug...I've been having this problem as well, although I don't have PowerTools or Crystal Reports installed. I suspect that it's something to do with xml files opened in the editor when it tries to start up. I was able to open the solution after deleting the .suo and .csproj.user files from the physical folders.<br /><br />At that point, the source control output shows the same number of 'Object reference not set to an instance of an object' messages as the number of projects in the solution.Anonymoushttps://www.blogger.com/profile/00421160539054953028noreply@blogger.comtag:blogger.com,1999:blog-737100980526652029.post-74859679699212808752009-07-06T20:19:25.277-07:002009-07-06T20:19:25.277-07:00You also might find WCFStorm (http://www.wcfstorm....You also might find WCFStorm (http://www.wcfstorm.com) interesting. Its a test client for WCF services that can handle both load and functional test cases.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-737100980526652029.post-19043279075573915432009-06-29T04:35:08.554-07:002009-06-29T04:35:08.554-07:00Uberhelpful post! Thanks for sharing info.Uberhelpful post! Thanks for sharing info.k4millohttps://www.blogger.com/profile/15989791630372497661noreply@blogger.comtag:blogger.com,1999:blog-737100980526652029.post-79942054110928095162009-06-16T16:24:22.742-07:002009-06-16T16:24:22.742-07:00Had similar issue with web.config in my asp.net so...Had similar issue with web.config in my asp.net solution with Crystal Reports. VS would not load solution, but just crash.<br />businessObjects tags on the end of the config file was on one line. Edited with notepad placed CR in file and then solution would load.<br />PhilAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-737100980526652029.post-55662560601385764732009-06-05T04:41:44.335-07:002009-06-05T04:41:44.335-07:00Same problem for me. When the xaml file opened, th...Same problem for me. When the xaml file opened, the status bar showed: initializing toolbar and VS died. As it turned out, the toolbar had never been opened (fresh install on new laptop). Opening the toolbar first caused it to initialize and after that opening the xaml worked.Jeroennoreply@blogger.comtag:blogger.com,1999:blog-737100980526652029.post-73651085243600560082009-05-26T09:36:52.976-07:002009-05-26T09:36:52.976-07:00I was having a strange VS crashing issue when tryi...I was having a strange VS crashing issue when trying to open any xaml file in the designer. Just one project but VS just died with this exact same message.<br /><br />Uninstalling PowerTools cleared it up.<br /><br />Thanks for posting that info. I scratched my head all weekend over that when rebuilding the project didn't solve the problem.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-737100980526652029.post-3926647323326142682009-02-03T09:49:00.000-08:002009-02-03T09:49:00.000-08:00What exactly is the 'ServiceLocator' that you are ...What exactly is the 'ServiceLocator' that you are using?Anonymoushttps://www.blogger.com/profile/03255898942941268191noreply@blogger.comtag:blogger.com,1999:blog-737100980526652029.post-58921947386041783052008-11-27T00:46:00.000-08:002008-11-27T00:46:00.000-08:00Unit testing is not as so much a waste of time rat...Unit testing is not as so much a waste of time rather a time saver when you don't spend time on it.<BR/><BR/><B>Yes</B>, we know that is a misconception and we know that unit testing saves us time because we can ensure the quality of the code throughout the project.<BR/><BR/>On the other hand it takes some time and thinking to create the tests in the first place.<BR/><BR/>Like any type of testing comes in last in the planning (<I>and also with limited time</I>) there is usually no real time allocated for building unit tests. If the unit tests are on the list of tasks they usually are prioritized well below the functionality tasks and then get moved onwards to the next realease. And then again.<BR/><BR/>But it's not just the project manager who keeps postponing unit tests. Also developers like building stuff that does something over stuff that just doesn't really do something.<BR/><BR/>We are still a long way away from Test Driven Development. We say we believe in it, but we do not practice our own believes.Anonymoushttps://www.blogger.com/profile/03880668956776986361noreply@blogger.comtag:blogger.com,1999:blog-737100980526652029.post-85035775765619237652008-11-26T17:17:00.000-08:002008-11-26T17:17:00.000-08:00I wholeheartedly agree. Unit testing only takes ti...I wholeheartedly agree. Unit testing only takes time if it's viewed as an extra activity. Degrading UT, the very best tool to guarantee software quality by thinking it's just some unnecessary and time-consuming bonus activity means the quality is not the priority for the management. Or that they are simply not willing and think that wishing upon a star takes care of that. Optimistic assumptions about quality are fine, but without UT they're just that and nothing more. Or perhaps they think their customers like buggy software and inside every customer is a little sw testing enthusiast. But it's not only managers, imagine how frustrating is to hear the same thing from your colleagues, programmers, who are supposed to "get it". I would say that's even worse. Well, if you can't change how the company works, change the company ;)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-737100980526652029.post-29380161712331215782008-11-26T09:11:00.000-08:002008-11-26T09:11:00.000-08:00Do you know the difference between Unit tests and ...Do you know the difference between Unit tests and Integration tests? I think you made an example of the integration test. I am not sure that big integration tests that tests the whole system with subsystems can be done in terms of bug fixing or development process without additional time involved. Unit tests that covers specific methods and classes can be done without any time expenses with replacing all the sub-systems with mock objects. Sometimes it can even speed the process of bug fixing. I am concerned that integration tests requires additional time to be spent.Koenig_Dublinhttps://www.blogger.com/profile/14637382954206291665noreply@blogger.comtag:blogger.com,1999:blog-737100980526652029.post-45417940413550211572008-11-26T08:08:00.000-08:002008-11-26T08:08:00.000-08:00What most people miss out of these is that they us...What most people miss out of these is that they usually pay the cost some where...<BR/><BR/>We don't have time for unit testing. Then something mistakenly makes it into production and the time is spent supporting the product instead.<BR/><BR/>We don't have time to break out code by interfaces, base classes.....but the time is spent finding, fixing and/or maintaining the same logic duplicated in multiple places.<BR/><BR/>I do not understand why or how people cannot associate these costs with decisions to cut time during development. I wish I did. Maybe then I could be more convincing as to why we should so something the "right way" up front.tatmanhttps://www.blogger.com/profile/07027824529635285617noreply@blogger.comtag:blogger.com,1999:blog-737100980526652029.post-16619503451325176622008-11-26T07:19:00.000-08:002008-11-26T07:19:00.000-08:00Well said. It reminds me of the old analogy "I've ...Well said. It reminds me of the old analogy <BR/>"I've got no time to sharpend the saw. I'm too busy sawing!" :-)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-737100980526652029.post-82290827853033892562008-11-10T23:34:00.000-08:002008-11-10T23:34:00.000-08:00Well said.Well said.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-737100980526652029.post-10894806677924148362008-06-20T03:02:00.000-07:002008-06-20T03:02:00.000-07:00Hi Marcel,The question that I have after reading y...Hi Marcel,<BR/><BR/>The question that I have after reading your post is; What do you mean with "totally agile" if you contrast if with "just enough"? Can I actually build something that is totally agile? <BR/><BR/>In your other post about SOA you link to "SOA in the Real World", there is the statement: With SOA, integration becomes forethought rather than afterthought.<BR/><BR/>I believe that is all there is.<BR/>It provides the flexibility that everyone needs, at no extra cost.<BR/><BR/>Unfortunately, marketeers and sales people are inflating these basics to the "hyper agility" message.<BR/><BR/>I think it is a big mistake to (based on that inflation) turn around and say: Just tell me what to integrate with, and I will design "just enough" integration for those integrations. That kills flexibility right from the start.<BR/><BR/>So lets just continue do what SOA is supposed to do: Design the application to be integratable, to support process changes and integrations not anticipated initially.Theo Stolkerhttps://www.blogger.com/profile/04508207645563583035noreply@blogger.com