﻿<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Sanjay Mehrotra</title>
    <description>My personal DotNetNuke blog.</description>
    <link>http://www.dotnetnuke.com/Products/Development/Forge/ProviderFirebird/tabid/909/BlogId/75/Default.aspx</link>
    <language>en-US</language>
    <managingEditor>smehrotra@acuitisolutions.com</managingEditor>
    <webMaster>admin1@dotnetnuke.com</webMaster>
    <pubDate>Fri, 04 Jul 2008 22:17:33 GMT</pubDate>
    <lastBuildDate>Fri, 04 Jul 2008 22:17:33 GMT</lastBuildDate>
    <docs>http://backend.userland.com/rss</docs>
    <generator>Blog RSS Generator Version 3.4.0.39853</generator>
    <item>
      <title>Almost there with new Feedback Release and other end of year reflections</title>
      <description>&lt;p&gt;After about two months of testing and re-submitting of the feedback module to the release tracker for approval, I can finally say that I think I see the light at the end of the tunnel. With the very rigorous testing which both Sebastian and Matthias have put the new feedback module through, I am hoping that this is going to be a much better module than it's predecessor. &lt;br /&gt;
A big thank you goes to both of them for guiding me along the way and ensuring that I was able to "fix" a lot of the legacy issues that I had inherited from the 3x version of the module.&lt;br /&gt;
Some of the things which I've learnt as part of the release process which might be helpful to others down the road include&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;&lt;strong&gt;Make sure to clean up gemini issues as pertains to your module&lt;/strong&gt; - A big shout out goes to Alex for being the Gemini Watch dog on this and ensuring that all t's are crossed and i's are dotted....&lt;/li&gt;
    &lt;li&gt;&lt;strong&gt;Make sure you update your release notes to match the Gemini Issues.&lt;/strong&gt;&lt;/li&gt;
    &lt;li&gt;&lt;strong&gt;Double check and triple check your SQL scripts&lt;/strong&gt; - Since Sebastian personally looks through this and he's a SQL Server expert, remember that he'll find stuff that you'd think are ok due to prior "passes" on your module but are no longer acceptable. I have personally found this to be a great step in the right direction to the extent that it has got me in the mode of doing the same for my oracle provider which I think is a very positive thing.&lt;/li&gt;
    &lt;li&gt;&lt;strong&gt;Don't be surprised/dissapointed if you get multiple "failed module" emails from release tracker&lt;/strong&gt;. With regards to the feedback module, I think I can safely say that it must have been resubmitted at least 8-10 times since October when i first started the submission process. Initially I thought that this would be a reflection of my poor coding skills on the module itself but this has not been the case. Most of the times the module was failed because of "legacy" issues which were finally being cleaned up in the new 4.4.2 version. I am expecting that with future releases this amount of re-submitting tapers off since we have got most if not all of the legacy issues out of the way.&lt;/li&gt;
    &lt;li&gt;
    &lt;div align="left"&gt;
    &lt;p&gt;&lt;strong&gt;Work towards getting your module to be XHTML compliant. &lt;/strong&gt;This is not yet a requirement from the core but I had already started doing this with some of my other DNN projects and it was relatively easy to make the neccessary changes to the feedback module too. Most of this is very simple stuff like closing out your &lt;BR&gt; tags and using lower cases instead of upper cases with HTML elements. A big thank you goes to Timo Breumelhof with helping me out with the testing of this aspect.&lt;br /&gt;
    &lt;br /&gt;
    &lt;br /&gt;
    I am sure there are other things I can mention with regards to the testing process but these are a couple that come to mind immediately.&lt;br /&gt;
    &lt;br /&gt;
    This has also been a very interesting year for me and as we start winding down the days for the year, I wanted to pause and reflect on some of the positive things in my life that have occured this year. My little baby boy was born on March 19th which was one of the most happiest moments in my life. With each passing day I learn new things about babies which I had no idea about which is always exciting. One of the most positive things I've learnt this year is to be more patient - and I attribute this completely to being a dad. I can go on and on about this aspect alone but will leave it at just that :).&lt;/p&gt;
    &lt;p&gt;Professionally, this has been a good year too. I have been very fortunate to be on a huge DNN project for the health care industry which went live on September 1st, 2007 and has thus far had 3 point releases which added a ton of features to the application. Being part of this project has helped me understand the dynamics invovled in managing a huge enterprise level web application project which had over 50 people as part of the team and had different components to it which were outside my team's control. From managing source control to deploying builds, it has been a very good learning experience and I can definetely say that I am ready for the next HUGE DNN project without any hesistation at all.&lt;br /&gt;
    &lt;br /&gt;
    As I reflect on the year, I also would like to pause and think of things that have happened and how I could have done things differently and one of the areas that comes to mind is my invovlement with the feedback module as well as DotNetNuke in general. I will start off by saying that I know I could have done a better job with the feedback module. Part of my problems were work related - being overwhelmed with daunting deadlines to be met. The other part was underestimating what effort would be required to be able to be an effective "Project Lead" for the feedback module. When I was first asked to join as a Project lead, I had completely misunderstood this to be a simple effort with some time spent on the updates for the module as well as responding to questions/issues on the website.  However, when you factor in the time and effort put into doing just these mentioned items together with being a full time dad and having another two full time jobs (my real job and also managing the oracle data providers for DotNetNuke), it becomes imperative that one fully understands what "time management" really means. I am hoping that with some of the changes I've made in my personal life I can better manage my responsibilities here as well as in other aspects of my life, but only time as well as input from others will tell. I'm always open to suggestions and constructive criticism and hopefully I can make 2008 to be a much better year for myself as well as for the feedback module in general....&lt;/p&gt;
    &lt;p&gt; &lt;/p&gt;
    &lt;/div&gt;
    &lt;/li&gt;
&lt;/ul&gt;</description>
      <link>http://www.dotnetnuke.com/Products/Development/Forge/ProviderFirebird/tabid/909/EntryID/1685/Default.aspx</link>
      <author>smehrotra@acuitisolutions.com</author>
      <comments>http://www.dotnetnuke.com/Products/Development/Forge/ProviderFirebird/tabid/909/EntryID/1685/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.dotnetnuke.com/Default.aspx?tabid=909&amp;EntryID=1685</guid>
      <pubDate>Thu, 20 Dec 2007 15:00:36 GMT</pubDate>
      <slash:comments>12</slash:comments>
      <trackback:ping>http://www.dotnetnuke.com/DesktopModules/Blog/Trackback.aspx?id=1685</trackback:ping>
    </item>
    <item>
      <title>New Updates for the feedback Module (version 4.4.2)</title>
      <description>&lt;p&gt;After a long hiatus, I can now return to the changes for the feedback module as I had intended. Part of the delay in getting out the newer version has been my fault - switching jobs and trying to adjust to the new job culture. The other part has also been trying to adjust to having a new baby in the house which in itself is a huge project. :)&lt;br /&gt;
For this I do apologize to everyone in the community in general and hope to correct this in the upcoming weeks/months by being more proactive in my approach.&lt;br /&gt;
There are a couple of changes for 4.4.2 of the feedback module which have been submitted for approval to the core via the release tracker.  One of the major changes has been the ability to setup moderation roles so that people besides the Site Administrator can moderate posts submitted via the feedback form. This brings the project in line with for example the repository module and forums module which offers similar capabilities.&lt;br /&gt;
I have also added the stubs for creating the same capability for Lists creations (subjects and categories) and the goal here is that if I receive positive feedback regarding the moderation roles, I will extend this same capability to the Lists Creation section too.&lt;br /&gt;
Another major enhancement for 4.4.2 has been the ability to setup categories as email send to addresses. This means that you can setup multiple email addresses as a category and when the feedback is submitted, it will now be sent to multiple email destinations. This allows for one to create different email destinations based on the category (which I believe was a feature request when 4.4.1 came out).&lt;br /&gt;
There are other minor changes in this version including the ability to modify the items displayed in the view comments section (namely the ability to hide/show the name/email and subjects) of submitted feedback posts as well as some general cleanup to the subject id's, category ids which were being sent/viewable from certain areas instead of the values for these fields.&lt;br /&gt;
&lt;br /&gt;
I am not sure how long the release process will take but I am hoping that in the coming days, I will be able to get the 4.4.2 version of the module released for general consumption. I already have the version 4.4.3 in the works which will include a new administration interface which will allow for the creation of new feedback form fields.&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;p&gt;Sanjay Mehrotra&lt;/p&gt;</description>
      <link>http://www.dotnetnuke.com/Products/Development/Forge/ProviderFirebird/tabid/909/EntryID/1583/Default.aspx</link>
      <comments>http://www.dotnetnuke.com/Products/Development/Forge/ProviderFirebird/tabid/909/EntryID/1583/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.dotnetnuke.com/Default.aspx?tabid=909&amp;EntryID=1583</guid>
      <pubDate>Sun, 07 Oct 2007 14:20:57 GMT</pubDate>
      <slash:comments>2</slash:comments>
      <trackback:ping>http://www.dotnetnuke.com/DesktopModules/Blog/Trackback.aspx?id=1583</trackback:ping>
    </item>
    <item>
      <title>Update on Feedback Module and other items pertaining to feedback Module</title>
      <description>&lt;p&gt;First off, my apologies for being AWOL for a couple of days. I have a 37 week pregnant wife and although her pregnancy has been un-eventful till date, it's finally beginning to become eventful. She might have a kidney infection and I was in the hospital with her for a couple of days... &lt;/p&gt;
&lt;p&gt;Now, with regards to the feedback module- the hold up has been 100% because of me. The core had sent me notification that the source version was failing installation and that's why it was being held up. However I could not respond to their notification till earlier today and was able to quickly resolve the problem. &lt;/p&gt;
&lt;p&gt;Here's the problem - the core requires the source version to be installable exactly like the install version on any DNN site. This means that it needs to have it's own manifest file (*.dnn) which will then instruct the PA Installer on how to place the files in the right folders. Since I chose to use the project method for creating the feedback module (i.e has a compiled dll instead of the source being placed in the app_resources folder), I have to get the source version to place the right project files in the right places. As everyone might be aware, the project files typically have an AssemblyInfo.vb file. &lt;br /&gt;
The problem arose when the PA Installer tries to parse the AssemblyInfo.vb files - since there are two files with the same name, they get overridden. &lt;br /&gt;
The fix for this is creating another zip file (I called it resources.zip) which contains the vbproj and vb source files). Inside this zip file, I had to maintain the folder structure for the project which allowed the PA Installer to correctly place the files in the right places....&lt;br /&gt;
&lt;br /&gt;
I also use NANT to automate the building process and I had a small bug in my NANT script which was not including the resx files in the source version......&lt;br /&gt;
&lt;br /&gt;
I uploaded the fixes earlier today and the core has now been able to verify my changes. I am hoping that there are no more hold ups and we should be ready to release this (hopefully this week)... &lt;br /&gt;
If someone is having problems waiting for the official release, please feel free to contact me and I can see how to work with you personally to get your problem solved...&lt;/p&gt;
&lt;p&gt;Sanjay&lt;/p&gt;</description>
      <link>http://www.dotnetnuke.com/Products/Development/Forge/ProviderFirebird/tabid/909/EntryID/1311/Default.aspx</link>
      <comments>http://www.dotnetnuke.com/Products/Development/Forge/ProviderFirebird/tabid/909/EntryID/1311/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.dotnetnuke.com/Default.aspx?tabid=909&amp;EntryID=1311</guid>
      <pubDate>Thu, 22 Feb 2007 08:00:00 GMT</pubDate>
      <slash:comments>6</slash:comments>
      <trackback:ping>http://www.dotnetnuke.com/DesktopModules/Blog/Trackback.aspx?id=1311</trackback:ping>
    </item>
    <item>
      <title>Feedback module passed the release tracking program</title>
      <description>&lt;p&gt;The feedback module has just passed the release tracking program and I'm expecting it to be available very shortly. I have to find out from the core whether there is a beta testing period or whether it is released as is to the general community.&lt;br /&gt;
I was able to sneak in the captcha features in the upcoming release (v 4.04.01) and it is exciting to see some of the feedback generated by the community on features they would like to see in upcoming versions. &lt;br /&gt;
&lt;/p&gt;</description>
      <link>http://www.dotnetnuke.com/Products/Development/Forge/ProviderFirebird/tabid/909/EntryID/1302/Default.aspx</link>
      <comments>http://www.dotnetnuke.com/Products/Development/Forge/ProviderFirebird/tabid/909/EntryID/1302/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.dotnetnuke.com/Default.aspx?tabid=909&amp;EntryID=1302</guid>
      <pubDate>Mon, 12 Feb 2007 08:00:00 GMT</pubDate>
      <slash:comments>7</slash:comments>
      <trackback:ping>http://www.dotnetnuke.com/DesktopModules/Blog/Trackback.aspx?id=1302</trackback:ping>
    </item>
  </channel>
</rss>