Visual Studio Managed Package Framework for Projects (MPFProj)

Source code checked in, #69709

Project Collection Service Accounts — Mon, 01 Oct 2012 22:10:56 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #69708

Project Collection Service Accounts — Mon, 01 Oct 2012 22:06:45 GMT

Checked in by server upgrade

Source code checked in, #52373

_TFSSERVICE — Wed, 28 Jul 2010 17:08:20 GMT

Checked in by server upgrade

Created Issue: Cast error when using custom logger. [18105]

tbonemike — Wed, 30 Jun 2010 18:54:55 GMT

I have my own logger class that inherits from Microsoft.Build.Utilities.Logger. This is part of my overall Package implementation in VS2008.
When I run I get a cast error in method SetOutputLogger on this line in ProjectNode.cs --> ((IDEBuildLogger)this.BuildLogger).OutputWindowPane = output;
"Unable to cast object of type Idea.Xgen.XgenLogger.XgenLogger to type Microsoft.VisualStudio.Project.IDEBuildLogger".
I had reported this in the past for VS2005 and it was suggested to get around it for the time being with an IF statement before --> if (this.buildLogger is IDEBuildLogger)
Is this something that needs to be fixed the the MFP source or do I have a bug in my implementation?

Thanks

Patch Uploaded: #5239

bralston7 — Wed, 10 Feb 2010 20:12:49 GMT

bralston7 has uploaded a patch.

Description:
The attached code enables "Add as Link" functionality for projects. I do not take credit for this code. 99% of this code is taken from the Wix Votive source, build 3.0.5419.

New Post: For Visual Studio 2010, please use site : http://mpfproj10.codeplex.com/

selmai — Tue, 09 Feb 2010 19:35:51 GMT

This site is dedicated for VS 2008 MPFProj discussions. If you’re using VS 2010, we now have source code available for Release Candidate at http://mpfproj10.codeplex.com/ site.

Commented Issue: Enhancement Request: Support "Add File as Link" functionality [16236]

bralston7 — Mon, 08 Feb 2010 21:45:38 GMT

The MPF should support the ability to "Add as Link" when adding files to a project, just like C# projects do. The Wix Votive project already modified the MPF to do this, and I would be happy to merge in the changes if this is assigned to me.
Comments: ** Comment from web user: bralston7 **

I have changes ready to merge for this enhancement. Moderators, please let me know how I can contribute these changes for review.

Created Issue: Enhancement Request: Support VS2005 SDK [16237]

bralston7 — Wed, 03 Feb 2010 22:39:07 GMT

The MPF can be modified via conditional compilation args (ie. #ifDef VS2005) to work for both VS2005 and VS2008. The Wix Votive project has already done this. I would like to see this change merged into the MPF. This would be very useful for those of us developing extensions for both 2005 and 2008.

Created Issue: Enhancement Request: Support "Add File as Link" functionality [16236]

bralston7 — Wed, 03 Feb 2010 22:36:11 GMT

New Post: Customise properties for certain file types

DmitryPavlov — Tue, 13 Oct 2009 11:26:06 GMT

You are welcome, Mike!

1. You should write in you custom project class code like this:

public override FileNode CreateFileNode(ProjectElement item)
    {
      if (item == null)
      {
        throw new ArgumentNullException("item");
      }
      return new YourCustomFileNode(this, item);
    }

2. Inherit YourCustomFileNode class from MPF FileNode class

3. Override NodeProperties creation in custom file node:

protected override NodeProperties CreatePropertiesObject()
    {
      return new YourCustomFileNodeProperties(this);
    }

4. And inherit YourCustomFileNodeProperties from MPF FileNodeProperties class

NOTE: I'm not sure it is correct but I remember right I had problems with custom properties class until I added this property to it:

     [Browsable(false)]
       public string SubType
       {
           get
           {
               return Node.SubType;
           }
           set
           {
               Node.SubType = value;
           }
       }

Hope that saves the time.

Another tip - to understand how to expose properties - look at the implementation of some MPF NodeProperties class inheritors.

Best wishes,

Dmitry Pavlov

New Post: Customise properties for certain file types

mikeyg — Tue, 13 Oct 2009 11:12:35 GMT

Hi Dmitry,

We use a custom project type.

Your suggestion in point 2 is exactly what I was looking for!

Thanks very much!

Mike

New Post: Customise properties for certain file types

DmitryPavlov — Tue, 13 Oct 2009 10:02:52 GMT

Hi Mike,

I'm not I understood the situation yet, so I'd like to ask some questions to understand it:

1. Do you use custom project type based or you extend C# or other project types?

2. In case your answer for Q1 - did you tried to create different custom FileNode inheritors and override NodeProperties for them with specific set of properties for different file types?

Best wishes,

Dmitry Pavlov

New Post: Customise properties for certain file types

mikeyg — Tue, 13 Oct 2009 09:50:34 GMT

Hi,

My team use a custom project type and I want to add custom properties to the properties window depending on the file extension or file type. e.g. if its a css file then I want to see an extra property that is specific to that file type. Same would apply to js files etc.

So we have our own version of the SingleFileGeneratorNodeProperties class which allows us to add properties, but this will mean that these properties are available for all file types, when we would like to make them specific as mentioned above.

Please help.

Thanks,

Mike

Commented Issue: Building source causes hard error CA0001 -- exception thrown by FxCop [11507]

petterh — Mon, 28 Sep 2009 15:27:49 GMT

Building this set of source files with code analysis turned on causes a hard error whose message says:
Error 13 CA0001 : Rule=Microsoft.Naming#CA1725, Target=Microsoft.VisualStudio.Project.Automation.OAReferenceBase`1.#get_Extender(System.String) : Object reference not set to an instance of an object. MPFProj

Suppressing the rule in source or in the global suppressions file does _not_ work around this error, but turning off this error in the Code Analysis settings for the project does.

Please modify the source to avoid triggering the rule. I will also post this to the FxCop forums so they can address the problem with rule 1725.
Comments: ** Comment from web user: petterh **

It seems to me this is an issue with FxCop rather than with MPFProj...?

Commented Issue: Building source causes hard error CA0001 -- exception thrown by FxCop [11507]

petterh — Mon, 28 Sep 2009 15:26:13 GMT

Impact = Low is wrong: For us it's a showstopper. Turning off the error in the Code Analysis section for the project helps when you do Run Code Analysis from within Visual Studio, but not when you use msbuild.

New Post: How to control the contex menu over the FileNode

kobrigo — Wed, 20 May 2009 08:15:03 GMT

Hi all,

I have been trying to modify the context menu that opens when you right-click on a file node.

Specifically I am trying to remove the rename command from that menu. My cusrom project should not enable changing the name of some of the files.

I was able to remove the command from the context menu with changing the function in HierarchyNode called:

protected virtual QueryStatusResult QueryStatusCommandFromOleCommandTarget(Guid cmdGroup, uint cmd, out bool handled)

I've removed the line

case VsCommands.Rename:

This function is being called if the call has originated from QueryStatus of the IOleCommandTarget interface. but there is anothen similar function called QueryStatusCommand of the IVsUIHierarchy interface.

My question is: how can I know when these functions are being called and what commands should be blocked in what function?

Thanks in advnace

Eyal

Created Issue: Wrong project reference icon is shown in solution explorer (VS2008)

bdicroce — Mon, 11 May 2009 21:11:11 GMT

When adding a project reference (C++, Visual Basic, etc.) to another project in Solution Explorer (right-click project's reference, then click on the Add Reference... menu item), the icon being displayed is not the standard greyish component icon.

In fact, the icon being displayed is the project's icon (The C++ project icon for a C++ reference, for example). We fixed the problem by adding the following instructions at line 143 in the ProjectReferenceNode.cs:

if( prj.Properties == null )
continue;

Here's a sample of part of the current code with our solution from above, so that you can easily search for already existing strings:

//Skip this project if it is an umodeled project (unloaded)
if(string.Compare(EnvDTE.Constants.vsProjectKindUnmodeled, prj.Kind, StringComparison.OrdinalIgnoreCase) == 0)
{
continue;
}

// Get the full path of the current project.
EnvDTE.Property pathProperty = null;
try
{
// OUR SOLUTION BEGINS HERE
if( prj.Properties == null )
continue;
// OUR SOLUTION ENDS HERE
pathProperty = prj.Properties.Item("FullPath");
if(null == pathProperty)
{
// The full path should alway be availabe, but if this is not the
// case then we have to skip it.
continue;
}
}

New Post: Flavored "Outer" Project

flagrant99 — Fri, 01 May 2009 18:15:11 GMT

It appears MPF (Managed Package Framework) is much larger than just MPFProj (Microsoft.VisualStudio.Package). MPFProj is ONLY used for "Inner" "REAL" custom Projects. If you want to flavor MPFProj will not help.

New Post: Flavored "Outer" Project

flagrant99 — Tue, 28 Apr 2009 15:10:11 GMT

Why does MPF only support "Inner" "REAL" custom Projects and NOT Flavored "Outer" Project like FlavoredProjectFactoryBase/FlavoredProjectBase from VS 2008 SDK. In other words why are these in seperate SDK's?

Commented Issue: OAProperties.Item can't find "URL" index

cmaxo — Mon, 27 Apr 2009 22:12:34 GMT

I'm creating a language service for a simple DSL. While working in the experimental hive, MPFProj quite often throws an exception in OAProperties.Item when the index argument equals "URL". The call stack shows nothing but [External Code] and this function. The exception occurs when I close the solution or exit Visual Studio, but it also occurs sometimes when I open the project. I can't seem to determine the origin of the "URL" property, why it's needed, or how to provide it.
Comments: ** Comment from web user: cmaxo **

I found a solution to this problem without having to modify the cs files provided by this project. The file type that I was adding needed to have a class that "presents" properties to visual studio and that class needs to have a "public string URL..." property. The class that I created that subclasses from FileNode has this method now:

protected override NodeProperties CreatePropertiesObject()
{
MyFileNodeProperties properties = new MyFileNodeProperties(this);
properties.OnCustomToolChanged += new EventHandler<HierarchyNodeEventArgs>(OnCustomToolChanged);
properties.OnCustomToolNameSpaceChanged += new EventHandler<HierarchyNodeEventArgs>(OnCustomToolNameSpaceChanged);
return properties;
}

And MyFileNodeProperties has among other things the URL property.

Corey