...accommodate any type of software that is device dependent and would possibly need manipulation of data. People often compare .Net to Java when it comes to programming language. Unfortunately this comparison is not valid, integration is possible without having to rebuild like in Java. The .Net Framework manages memory to prevent overflow and requires the use of verifiable safety so there is less data corruption. With .Net error handling is also much easier. In this article it also states that .Net has a much simpler application build, debugging and deployment platform which would make the program more user friendly. Programmers are able to view the application while they are building it. .Net is versatile and makes programming a lot faster. DQ2 WK1 In the article a difference was in the refactoring section, it states that with XP the programmers revise their product designs and the underlying architecture on a continuous basis which would allow accommodations to new functionalities and also put a stop to redundancy in coding. With Microsoft, well everything is pretty much based off observations and interactions with the product. By creating daily builds, the Microsoft types believe this is how they are able to show progress before releasing the Beta version. In another section, “Simple Design” states that with XP teams the process is “ Build only what the User needs” not what the future may possibly hold. Between the two approaches, I am torn. I would like to say I would blend...
Words: 1194 - Pages: 5