I had a problem to register new addins in Visual Studio .NET 2003 that I exposed there : Refactoring my publishing tool. When I was starting Visual Studio .NET 2003 I got this dialog:
Continue readingI refactored quit a lot of code on my site Tech Head Brothers this week and went to bed late (around 1:30 AM each day). But now it is running better and faster. I removed the rendering to Pdf using NFop of the articles because it works locally on my TEST server but not on the PROD one.
One of the speed improvement is due to the complete reimplementation of a user control that download a RSS to publishnews on my site. The issue with the previous method was that the cache was buggy. Now what I am doing is to to use two values in cache, one is the RSS document (a XML document as a string) and that one never expire:
As I described in my last post I would like to have the possibility to edit only one method in the source code viewer and get to the code by browsing my class hierarchy through two windows exposing classes then methods, attributes…
Now I know why it was a problem from the guys at Microsoft to provide that feature:
Code view is cut from Whidbey HTML Editor
I finally managed to have my Addins in Visual Studio .NET 2003 working again, with reinstallation of it and then running a repair.
Then I installed ReSharper 0.81; I am part of the Early Access Program, and worked with it for a couple of hours. There is much more features then the older version I tried, and for the moment I am happy with it. It brings lots of added value that will be present in Whidbey in Visual Studio .NET 2003.
Continue readingI started some time ago to work on a new release of the tool I developed to publish content on my web site Tech Head Brothers. This new release will add the possibility for the author to directly post there article to the website.
This solution is using:
- Word 2003 with it XML features Continue reading
Thats a summary of the article from Dare Obasanjo on MSDN.
Classes with Fields or Properties that Hold XML
If a class has a field or property that is an XML document or fragment, it should provide mechanisms for manipulating the property as both a string and as an XmlReader.Methods that Accept XML Input or Return XML as Output
Methods that accept or return XML should favor returning XmlReader or XPathNavigator unless the user is expected to be able to edit the XML data, in which case XmlDocument should be used.Converting an Object to XML
If an object wants to provide an XML representation of itself for serialization purposes, then it should use the XmlWriter if it needs more control of the XML serialization process than is provided by the XmlSerializer. If the object wants to provide an XML representation of itself that enables it to participate fully as a member of the XML world, such as allow XPath queries or XSLT transformations over the object, then it should implement the IXPathNavigable interface.I recently participated to a great experience!!! Writing a book with 12 co-authors using Sharepoint. I wrote two chapters about the development with Visual Studio .NET 2003 for Sharepoint and one part of a chapter about the integration of Groove and Sharepoint. This book is now available, here.
I started to look at Infopath long time ago and was waiting for that solution. I was really surprised to see Infopath with something else then .NET to wrtie code for it. That’s over. :-)
Since I implemented a tool to write the article on my web site Tech Head Brothers based on Word 2003 and Visual Studio Toolkit I was waiting the toolkit for Infopath to be able to have a form to post News that will use WSE to handle secured connection to my site.
In this new version when you add a button you will get a dialog with a button “Edit from code” and when you click on it your get back to Visual Studio that already added a handler for you:
If you want to understand the different security aspect in Web Services I recommend you this new cool MSDN Article: How to use Web Services Enhancements 2.0 to implement security, trust, and secure conversations in Web services architecture.