Yes, we did it!
|
Thursday, April 1, 2010
Nearly 20 years of hard work by hundreds of people have made this machine a dream come true. Today, the LHC has delivered its first high-energy collisions to the experiments. The new data will give us an unprecedented tool to understand the Universe we live in. A few minutes ago in the CCCWe did it! The first high-energy collisions were achieved at 13.06 today at all four points of the LHC ring. Collisions occurred after a few attempts at injecting and ramping beams in the morning. Before the collisions, there was a mixture of excitement, expectation, fear and apprehension in the CERN Control Centre. Nobody had ever attempted to make two proton beams collide at 3.5 TeV before. Only Nature produces collisions like this routinely, in the processes that yield cosmic radiation, but in a way that makes it very difficult to extract meaningful data. Read more: Cern The Bulletin
Twitter Search Will Rank Tweets One Day – Topsy Does Already
|
In this edition of our weekly Twitter column I’d like to ridicule Twitter search. Yes, no mistake here. We know now, after I’ve predicted it a few weeks ago that
Twitter search will finally rank tweetsinstead of just showing the latest ones.Search Engine Land asked when the news Twitter search ranking will get live but they received a “no comment” kind of reply. Twitter search is at least 10 years late when it comes to search technology so a few weeks or months sooner or later do not matter. Also, who needs Twitter search? Read more: SEOptimize
Official site: Topsy
VMware ThinApp 4.5
|
חיכינו וחיכינו ובסוף זה קרה, VMware הוציאו גירסא חדשה של ThinApp – מוצר ה- Application Virtualization שלהם – שתומך ב- Windows 7 ו- Windows Server 2008 R2.
אז מה התחדש? * תמיכה ב- Windows 7(x32\x64)\Windows Server 2008 R2 – אין צורך לעשות Capture מחדש של האפלקיציות עם הגירסא החדשה, רק לעשות להם Rebuild מחדש כדי לעדכן את סביבת הריצה ואת פורמט החבילה. שימו לב ל- Relink, יכול לעזור מאוד בתהליך.
*
אפשרות ליצור MSI packages בגודל של יותר מ- 2 ג’יגה – עד כה הגודל המקסימלי בו היה ניתן “לסגור” חבילה בקובץ msi היה 2GB (זה גם דרך אגב הגבול של כל קובץ msi אחר). מעכשיו המגבלה הזאת הוסרה וגם זמן ההתקנה של החבילה אשר נסגרה ב- msi התקצר בכמעט חצי.
* שיפורים ב- I\O, שיתוף זיכרון, רוחב פס בשימוש בזמן ה- Streaming (סביבות ה- 50% פחות) וקיצור זמן הפעלת האפליקציה.
* אפשרות ללכידת האפקליציה גם ממחשב לא “נקי” – בדרך כלל כאשר אנחנו רוצים ליצור חבילה של אפליקציה, יש צורך לעשות זאת על גבי מחשב עד כמה שיותר נקי כדי שיהיה אפשר לבודד בצורה הטובה ביותר את האפליקציה אותו אנחנו רוצים ללכוד. היכולת החדשה מאפשרת לתהליך הלכידה להסתכל רק לקבצים וערכי ה- Registry שהאפליקציה ניגשת אליה בלי קשר להאם הם קיימים או לא בתחנה ממנה מבוצע תהליך הלכידה. כרגע זה נבדק רק עם VMware tools ש”מלכלכים” את התחנה ולא עם אפליקציות אחרות. ככה שנכון לעכשיו ההמלצה בקשר לסביבה בה נעשה תהליך הלכידה עומדת בעינה, יש להשתמש בסביבת עבודה נקיה ככל שניתן.
אז מה התחדש? * תמיכה ב- Windows 7(x32\x64)\Windows Server 2008 R2 – אין צורך לעשות Capture מחדש של האפלקיציות עם הגירסא החדשה, רק לעשות להם Rebuild מחדש כדי לעדכן את סביבת הריצה ואת פורמט החבילה. שימו לב ל- Relink, יכול לעזור מאוד בתהליך.
*
אפשרות ליצור MSI packages בגודל של יותר מ- 2 ג’יגה – עד כה הגודל המקסימלי בו היה ניתן “לסגור” חבילה בקובץ msi היה 2GB (זה גם דרך אגב הגבול של כל קובץ msi אחר). מעכשיו המגבלה הזאת הוסרה וגם זמן ההתקנה של החבילה אשר נסגרה ב- msi התקצר בכמעט חצי.
* שיפורים ב- I\O, שיתוף זיכרון, רוחב פס בשימוש בזמן ה- Streaming (סביבות ה- 50% פחות) וקיצור זמן הפעלת האפליקציה.
* אפשרות ללכידת האפקליציה גם ממחשב לא “נקי” – בדרך כלל כאשר אנחנו רוצים ליצור חבילה של אפליקציה, יש צורך לעשות זאת על גבי מחשב עד כמה שיותר נקי כדי שיהיה אפשר לבודד בצורה הטובה ביותר את האפליקציה אותו אנחנו רוצים ללכוד. היכולת החדשה מאפשרת לתהליך הלכידה להסתכל רק לקבצים וערכי ה- Registry שהאפליקציה ניגשת אליה בלי קשר להאם הם קיימים או לא בתחנה ממנה מבוצע תהליך הלכידה. כרגע זה נבדק רק עם VMware tools ש”מלכלכים” את התחנה ולא עם אפליקציות אחרות. ככה שנכון לעכשיו ההמלצה בקשר לסביבה בה נעשה תהליך הלכידה עומדת בעינה, יש להשתמש בסביבת עבודה נקיה ככל שניתן.
Critical Device Database TIP
|
IntroductionHi everyone, Bob here. Today I thought we’d have a little discussion about the Critical Device Database (CDDB) in the registry and an issue that can be caused when a device is not contained there. This database stores configuration data for new devices that must be installed and started before the Windows components that normally install devices have been started. The idea behind the critical device database is to allow the installation of devices without using user mode plug-and-play manager. If a device is determined to be new, this database is queried to see if the information needed to install it are present. What was the issue?A customer was getting a Stop 0x7B (Inaccessible_Boot_Device) after they installed a BIOS update. Further investigation via the debugger using the !devnode command showed the following issue with a few devices: DevNode 0x8631f008 for PDO 0x8631f8e0 InstancePath is "PCI\VEN_15B3&DEV_5A44&SUBSYS_5A4415B3&REV_A1\6&38f4f1f2&0&00080310" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) Problem = CM_PROB_NOT_CONFIGUREDThe above device is a bridge, and according to the definition of CM_PROB_NOT_CONFIGURED, it does not have a ConfigFlags registry entry. I saw that this same problem occurred with a few bridges. If the bridge cannot be enumerated, devices on the bridge will not be discovered either. The Instance ID is used to look up the particulars such as driver name and class in the HKLM\System\CurrentControlSet\ENUM key in the registry. What happened here is the lookup failed and the system thought it was a new device. Since based on the device class this device was needed for boot, a Stop 0x7B occurred. What caused the issue?When the BIOS was updated the Instance ID included the version number of the bridge. The update increased the version number, so the Instance ID was changed.Read more: Ntdebugging Blog
Visual Studio Theme Generator
|
I just Got bored looking at the same code editor in Visual Studio. Same old white background and same syntax colour highlighting. So I give it a go and jump to Visual Studio options and start playing around with the option available to change the look and feel of the code editor. After trying for a while and working around with some customizations, I gave a second go and do a quick bing search in a hope that I will find some theme for my Visual Studio and Voila! I got one, not a theme but a tool indeed which allows me to customize theme as I want and the name is Visual Studio Theme Generator. It's an online free tool with some simple controls on the page which helps you in customizing your code editor by changing the main colour, background colour, foreground colour and also set he contrast. The tool also gives you the option to choose from a variety of colours. You can see the screenshot of this online tool below. Read more: {Midnight Programmer}
How to Build Mobile Websites with ASP.NET MVC 2 and Visual Studio 2010
|
Helped by the ubiquitous availability of low-priced mobile broadband plans, the "mobile Internet" is becoming more important than ever. The average cell phone user can easily place a bid on eBay, transfer money to their bank account in the Caymans, and check the score of last night's Springfield Isotopes game. For some businesses, having a mobile presence is unimportant, but for others it may represent an increasing percentage of their gross margin. Fortunately, the features provided by today's cutting-edge .NET Framework development platform make mobile web development easier than ever. This article will discuss the various mobile website options available today and show you how you can leverage Visual Studio (VS) 2010 and ASP.NET MVC's powerful features to get your mobile websites to market as quickly and easily as possible. Various Approaches to Building Mobile Websites
When it comes down to it, the term "mobile website" can mean many things to many people—and some of those definitions can conflict quite severely! The driving goals behind the experience you want to provide to your customers will also be the same drivers behind the technical implementation choices you make in creating that experience. At a high level, most mobile websites leverage one of the following approaches, listed roughly in order of technical difficulty. No mobile website at all. Many popular mobile devices are somewhat capable of displaying websites. If your site produces clean, standards-compliant markup with no advanced functionality, you may be able to get away with this option. Unfortunately, if you're reading this article, this approach probably does not apply to you. Standard website with mobile style sheets. If your site comes close to meeting the description presented in the first approach but falls short in a few areas, you might be able to close those gaps by augmenting your site with mobile style sheets. Mobile style sheets are Cascading Style Sheets (CSS) that you can add to the list of style sheets you send to all clients, yet will apply only to mobile devices. This approach is popular because it's deceptively simple and—like the first approach—seems to allow developers to essentially forget mobile devices, confident that both standard web browsers and mobile devices will be able to consume the content that you publish to the web. Unfortunately, this is not realistic. In addition to the fact that some mobile browsers don't include any CSS support at all, those that do may introduce a multitude of issues while attempting to display your pages. Create multiple different sites or a subsite. Under this third approach, the webmaster has abandoned attempts to share the same exact content and behavior on a mobile and primary website, deciding instead to host multiple autonomous sites. Although the additional overhead may be significant, the approach provides certain benefits. In fact, gaining the ability to focus your efforts on delivering the best experience for all consumers while avoiding compromises made on behalf of mobile devices is so alluring that this approach is incredibly popular. Use the same website to deliver the same content and behavior in different ways, based on the device. Traditionally, the most technically difficult and high-overhead approach to mobile development has been based around leveraging the same codebase and content to serve all visitors to your site. Under this approach, your website will detect mobile browsers and adapt the markup that it renders, personalizing the results for each supported browser. As you can imagine, this approach offers the best experience for all users since every page they view has been optimized for their device, while also providing the richest and most maintainable back-end solution for developers and IT administrators alike. As you can tell, all these approaches have their benefits, usually most evident in their ongoing maintenance costs. Unfortunately, the substantial overhead in using one of the more involved approaches to serve both mobile and desktop browser requests has caused many development teams to compromise and settle on a less-expensive approach, losing out on a great deal of benefit in the process. Luckily, the tools offered in VS 2010 and ASP.NET MVC make developing and maintaining codebases that can serve desktop and mobile website users at the same time easier than ever. ASP.NET MVC Makes Your Life Easier
The newest web framework out of Redmond is a pleasure to work with, making many of the most common web development tasks seem much easier and more straightforward. At the heart of it, ASP.NET MVC is essentially a set of extensions on top of the ASP.NET framework, yet it provides a much different approach to web development than Web Forms. Instead of leveraging the Web Forms' Page Controller pattern (tying views and back-end functionality closely together), ASP.NET MVC takes a different approach by separating the processing of web requests into three distinct responsibilities: the model, view, and controller. Read more: DevConnections
When it comes down to it, the term "mobile website" can mean many things to many people—and some of those definitions can conflict quite severely! The driving goals behind the experience you want to provide to your customers will also be the same drivers behind the technical implementation choices you make in creating that experience. At a high level, most mobile websites leverage one of the following approaches, listed roughly in order of technical difficulty. No mobile website at all. Many popular mobile devices are somewhat capable of displaying websites. If your site produces clean, standards-compliant markup with no advanced functionality, you may be able to get away with this option. Unfortunately, if you're reading this article, this approach probably does not apply to you. Standard website with mobile style sheets. If your site comes close to meeting the description presented in the first approach but falls short in a few areas, you might be able to close those gaps by augmenting your site with mobile style sheets. Mobile style sheets are Cascading Style Sheets (CSS) that you can add to the list of style sheets you send to all clients, yet will apply only to mobile devices. This approach is popular because it's deceptively simple and—like the first approach—seems to allow developers to essentially forget mobile devices, confident that both standard web browsers and mobile devices will be able to consume the content that you publish to the web. Unfortunately, this is not realistic. In addition to the fact that some mobile browsers don't include any CSS support at all, those that do may introduce a multitude of issues while attempting to display your pages. Create multiple different sites or a subsite. Under this third approach, the webmaster has abandoned attempts to share the same exact content and behavior on a mobile and primary website, deciding instead to host multiple autonomous sites. Although the additional overhead may be significant, the approach provides certain benefits. In fact, gaining the ability to focus your efforts on delivering the best experience for all consumers while avoiding compromises made on behalf of mobile devices is so alluring that this approach is incredibly popular. Use the same website to deliver the same content and behavior in different ways, based on the device. Traditionally, the most technically difficult and high-overhead approach to mobile development has been based around leveraging the same codebase and content to serve all visitors to your site. Under this approach, your website will detect mobile browsers and adapt the markup that it renders, personalizing the results for each supported browser. As you can imagine, this approach offers the best experience for all users since every page they view has been optimized for their device, while also providing the richest and most maintainable back-end solution for developers and IT administrators alike. As you can tell, all these approaches have their benefits, usually most evident in their ongoing maintenance costs. Unfortunately, the substantial overhead in using one of the more involved approaches to serve both mobile and desktop browser requests has caused many development teams to compromise and settle on a less-expensive approach, losing out on a great deal of benefit in the process. Luckily, the tools offered in VS 2010 and ASP.NET MVC make developing and maintaining codebases that can serve desktop and mobile website users at the same time easier than ever. ASP.NET MVC Makes Your Life Easier
The newest web framework out of Redmond is a pleasure to work with, making many of the most common web development tasks seem much easier and more straightforward. At the heart of it, ASP.NET MVC is essentially a set of extensions on top of the ASP.NET framework, yet it provides a much different approach to web development than Web Forms. Instead of leveraging the Web Forms' Page Controller pattern (tying views and back-end functionality closely together), ASP.NET MVC takes a different approach by separating the processing of web requests into three distinct responsibilities: the model, view, and controller. Read more: DevConnections
Stream Music and Video Over the Internet with Windows Media Player 12
|
* Windows Live ID
* UPnP or Port Forwarding enabled on your home router
* Media files added to your Windows Media Player libraryWindows Live IDSign up online for a Windows Live ID if you do not already have one. See the link below for a link to Windows Live. Read more: How-to-geek
New Malware Overwrites Software Updaters
|
Researchers at Bach Khoa Internetwork Security (BKIS), a Vietnamese security company, have found a new type of malware that 'masks itself as an updater for Adobe Systems' products and other software such as Java,' wrote BKIS analyst Nguyen Cong Cuong in a post on the company's blog. BKIS showed screenshots of a variant of the malware that imitates Adobe Reader version 9 and overwrites the AdobeUpdater.exe, which regularly checks in with Adobe to see if a new version of the software is available. Read more: Slashdot
Israel's Supreme Court Says Yes To Internet Anonymity
|
The Israeli Supreme Court ruled this week that there is no civil procedure to reveal the identity of users behind an IP address, and that until such procedure shall be legislated, all internet postings, even torturous, may remain anonymous. The 69-page decision acknowledges the right to privacy and makes internet anonymity, de-facto, a constitutional right in Israel. Justice Rivlin noted that revealing a person behind an IP address is 'an attempt to harness, prior to a legal proceeding, the justice system and a third party in order to conduct an inquiry which will lead to the revealing of a person committing a tort so that a civil suit could be filed against him. Read more: Slashdot
Court law: פסק-דין
Court law: פסק-דין
Process Explorer v12
|
This Process Explorer release includes several significant new features, including the showing the web hosted in IE8 processes in the process tooltip, display of a svchost’s service host category in its tooltip, mapping of service names to threads on the threads tab and TCP/IP tabs of the process properties dialog on Windows Vista and higher (thanks to Windows Internals 5th Ed. coauthor Alex Ionescu), a new.NET assembly information tab in the process properties dialog (thanks to Pete Sheill), as well as other improvements and bug fixes. Read more: Process Explorer v12
Using Solution Folders
|
Did you know there are special folders to help you organize large solutions? There is! They are called, appropriately enough, Solution Folders. To create one just Right-Click on your solution (or go to Project -> Add New Solution Folder) and you will see this in Solution Explorer: Simply give the folder a name and you are good to go. But so what? I mean, what can you actually DO with these things? Here is a list of stuff you can do: * Move or add projects to them. Solution Folders can be nested to create greater organizational structure.
* Add, delete, or rename Solution Folders at any time, if the organizational requirements of the solution change.
* Unload all projects in a Solution Folder to make them temporarily unavailable for building.
* Collapse or hide entire Solution Folders so that you can work more easily in Solution Explorer. Hidden projects are built when you build the solution.
* Apply the same policy to all the projects by setting the Policy File property for the Solution Folder.
* Build or rebuild all the projects. The projects are built in the order specified by the project dependencies. Read more: Visual Studio Tips and Tricks
Best Practices for Running Linux on Hyper-V
|
Organizations typically rely on heterogeneous data centers that use a variety of applications and operating systems. If your organization uses Linux and Windows® operating systems in your data center, Microsoft can help you standardize, simplify, and reduce the cost of deploying and managing different operating systems and applications through Hyper-V™, the Microsoft® hypervisor-based server virtualization platform that is included in the Windows Server® 2008 and Windows Server® 2008 R2 operating systems. Using Hyper-V, you can reduce the number of physical systems, decrease your management and administration costs, and even expand functionality and resilience by making your Linux systems highly available. You can also take advantage of Windows-based tools that can help simplify backups and recovery plans and that can make it easier to monitor uptime and services—these tools are available regardless of which operating system you are running. This white paper discusses the benefits of virtualizing Linux on Hyper-V, and it offers best practices for enhancing the performance of Linux as a guest operating system on a Hyper-V host. The paper also provides links for further information on the topics covered.Read more: MS Download
N-Body Modeling with NBody.net
|
As part of keeping up to speed with some of the deliverables the patterns & practices teams are shipping, notably Enterprise Library, Unity and Prism as well as some of the latest development practices, like domain driven design. So in some ways the whole project is a test bed and showcase for lots of ideas and new ways of writing code. In the end it’s turned out I’ve taken on a bunch of other challenges, like the Task Parallel Library and mixed language development with C#, F#, C++/CLI, C++, OpenMP and Nvidia’s CUDA platform to improve performance and DirectX 9 to get a better, faster visualization. While this is still very much a work in progress it’s now a fully working implementation.
Mixed language architectureThe underlying architecture hasn’t changed. It’s still a WPF application written using Prism 1.0 based modular approach and relies on Enterprise Library 4.1 for cross cutting concerns like logging, validation and configuration. The WPF UI and the domain model are built up using Unity’s dependency injection container which means a user can configure different initial setup criteria and integration engines on the fly. The key is picking the appropriate parts of the application and the appropriate language to implement them in. The two big reasons are performance and access to APIs not exposed easily through managed code.Read more: NBody.net
Mixed language architectureThe underlying architecture hasn’t changed. It’s still a WPF application written using Prism 1.0 based modular approach and relies on Enterprise Library 4.1 for cross cutting concerns like logging, validation and configuration. The WPF UI and the domain model are built up using Unity’s dependency injection container which means a user can configure different initial setup criteria and integration engines on the fly. The key is picking the appropriate parts of the application and the appropriate language to implement them in. The two big reasons are performance and access to APIs not exposed easily through managed code.Read more: NBody.net
No Assemblies Found Matching: assemblyname.dll
|
Have you ever run into an issue where you don’t seem to be able to get rid of that assembly in GAC no matter how many times you try to run GACUTIL or delete it from your Windows Explorer running as administrator? It probably frustrates the heck out of you and in addition it messes up the working of your application. You may resort to reinstalling your OS, deploying your assembly on a different machine, etc. Well, this issue has been a problem for me for some time. The issue here may relate to machine running x64 Windows. For my case, I’m running Windows Server 2008 R2 which is a x64 bit machine and I know this problem has also been an issue for my previous installation of Windows Server 2008 x64. I’m also running Visual Studio 2008. My assembly has been targeted to Any CPU. This issue of not able to uninstall your assembly may relate to the bitness of your assembly and the location of where your assembly has already been installed to. I want to share the solution that works in my environment. Hopefully, it will work in yours as well. Here are the steps.1. Launch your VS 2008 as Administrator
2. Create a Windows or Web project, in my case, it’s a SharePoint web part project
3. Try to add a reference to the project
4. Choose Browse tab.
5. Enter %windir%\assembly
6. Right click on the assembly I want to uninstall
7. Choose Uninstall
8. Click OK on the confirmation dialog
9. It should be uninstalled nowAs you can see, GACUTIL installed the assembly to GAC successfully. However, it could not uninstall it.Read more: Ted Heng's MSDN Blog
2. Create a Windows or Web project, in my case, it’s a SharePoint web part project
3. Try to add a reference to the project
4. Choose Browse tab.
5. Enter %windir%\assembly
6. Right click on the assembly I want to uninstall
7. Choose Uninstall
8. Click OK on the confirmation dialog
9. It should be uninstalled nowAs you can see, GACUTIL installed the assembly to GAC successfully. However, it could not uninstall it.Read more: Ted Heng's MSDN Blog
Subscribe to:
Posts (Atom)
Posts
