Im developing custom DataFlow Component with my own UI Editor.
When I want to debug this component, I have to:

1. Uninstall old assembly from GAC
2. Change version in AssemblyVersion attribute
3. Change version in DtsPipelineComponent.UITypeName attribute
4. Recompile component
5. Install recompiled component to the GAC
5. Remove component from toolbox of the Visual Studio (Business Intelligence
Development Studio)
6. Remove old component from data flow
7. Add new component to the toolbox
8. Add component from toolbox to the DataFlow
9. Attach to Process - Visual Studio (Component Development) to the SSIS
package development

And then I can to debug the changes i did...

My question is: Do I have to do all those things to debug this component?
Is there any other way to debug it?
Simplier???

Thanks for response.

P.S.: Post-build command automatization with gacutil to unistall and install
assembly I have done.

Im posting it again because of nospam alias rules (First time i had no
nospam alias created)

Hi Mike,
Thank you for using Microsoft MSDN Managed Newsgroup. This is Charles. I will assist you on this thread.

Regarding your question, Do I have to do all those things to debug this component?
I think that your question is not a simple debugging scenario. Apparently you are experiencing a process of both re-
deployment and debugging. The debugging step is actually just your step 9. The other steps are for deployment of your
custom component. For the process of deployment, yes, the steps 1-8 are necessary for manual deployment. If you want
to simplify the steps, I think that you may consider creating a command batch file (.bat) to process your steps 1-5. You
may need to write an executable to change the version in your AssemblyVersion attribute and
DtsPipelineComponent.UITypeName, and recompile component. From some .NET experts, I know that you can use some
.NET SDK tools such as vbc.exe and csc.exe to compile an assembly.

The following articles are for developing, deploying and debugging custom objects for SSIS, and from which we can find
that there are indeed many steps required:
Building, Deploying, and Debugging Custom Objects
http://msdn.microsoft.com/en-us/library/ms403356.aspx
Developing a User Interface for a Data Flow Component
http://msdn.microsoft.com/en-us/library/ms136029.aspx

Hope this helps. If you have any other questions or concerns, please feel free to let me know. Have a nice day!

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...#notifications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Mike,
Thank you for using Microsoft MSDN Managed Newsgroup. This is Charles. I will assist you on this thread.

Regarding your question, Do I have to do all those things to debug this component?
I think that your question is not a simple debugging scenario. Apparently you are experiencing a process of both re-
deployment and debugging. The debugging step is actually just your step 9. The other steps are for deployment of your
custom component. For the process of deployment, yes, the steps 1-8 are necessary for manual deployment. If you want
to simplify the steps, I think that you may consider creating a command batch file (.bat) to process your steps 1-5. You
may need to write an executable to change the version in your AssemblyVersion attribute and
DtsPipelineComponent.UITypeName, and recompile component. From some .NET experts, I know that you can use some
.NET SDK tools such as vbc.exe and csc.exe to compile an assembly.

The following articles are for developing, deploying and debugging custom objects for SSIS, and from which we can find
that there are indeed many steps required:
Building, Deploying, and Debugging Custom Objects
http://msdn.microsoft.com/en-us/library/ms403356.aspx
Developing a User Interface for a Data Flow Component
http://msdn.microsoft.com/en-us/library/ms136029.aspx

Hope this helps. If you have any other questions or concerns, please feel free to let me know. Have a nice day!

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...#notifications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Mike,
Thank you for using Microsoft MSDN Managed Newsgroup. This is Charles. I will assist you on this thread.

Regarding your question, Do I have to do all those things to debug this component?
I think that your question is not a simple debugging scenario. Apparently you are experiencing a process of both re-
deployment and debugging. The debugging step is actually just your step 9. The other steps are for deployment of your
custom component. For the process of deployment, yes, the steps 1-8 are necessary for manual deployment. If you want
to simplify the steps, I think that you may consider creating a command batch file (.bat) to process your steps 1-5. You
may need to write an executable to change the version in your AssemblyVersion attribute and
DtsPipelineComponent.UITypeName, and recompile component. From some .NET experts, I know that you can use some
.NET SDK tools such as vbc.exe and csc.exe to compile an assembly.

The following articles are for developing, deploying and debugging custom objects for SSIS, and from which we can find
that there are indeed many steps required:
Building, Deploying, and Debugging Custom Objects
http://msdn.microsoft.com/en-us/library/ms403356.aspx
Developing a User Interface for a Data Flow Component
http://msdn.microsoft.com/en-us/library/ms136029.aspx

Hope this helps. If you have any other questions or concerns, please feel free to let me know. Have a nice day!

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...#notifications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Mike,
Thank you for using Microsoft MSDN Managed Newsgroup. This is Charles. I will assist you on this thread.

Regarding your question, Do I have to do all those things to debug this component?
I think that your question is not a simple debugging scenario. Apparently you are experiencing a process of both re-
deployment and debugging. The debugging step is actually just your step 9. The other steps are for deployment of your
custom component. For the process of deployment, yes, the steps 1-8 are necessary for manual deployment. If you want
to simplify the steps, I think that you may consider creating a command batch file (.bat) to process your steps 1-5. You
may need to write an executable to change the version in your AssemblyVersion attribute and
DtsPipelineComponent.UITypeName, and recompile component. From some .NET experts, I know that you can use some
.NET SDK tools such as vbc.exe and csc.exe to compile an assembly.

The following articles are for developing, deploying and debugging custom objects for SSIS, and from which we can find
that there are indeed many steps required:
Building, Deploying, and Debugging Custom Objects
http://msdn.microsoft.com/en-us/library/ms403356.aspx
Developing a User Interface for a Data Flow Component
http://msdn.microsoft.com/en-us/library/ms136029.aspx

Hope this helps. If you have any other questions or concerns, please feel free to let me know. Have a nice day!

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...#notifications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Mike,
Thank you for using Microsoft MSDN Managed Newsgroup. This is Charles. I will assist you on this thread.

Regarding your question, Do I have to do all those things to debug this component?
I think that your question is not a simple debugging scenario. Apparently you are experiencing a process of both re-
deployment and debugging. The debugging step is actually just your step 9. The other steps are for deployment of your
custom component. For the process of deployment, yes, the steps 1-8 are necessary for manual deployment. If you want
to simplify the steps, I think that you may consider creating a command batch file (.bat) to process your steps 1-5. You
may need to write an executable to change the version in your AssemblyVersion attribute and
DtsPipelineComponent.UITypeName, and recompile component. From some .NET experts, I know that you can use some
.NET SDK tools such as vbc.exe and csc.exe to compile an assembly.

The following articles are for developing, deploying and debugging custom objects for SSIS, and from which we can find
that there are indeed many steps required:
Building, Deploying, and Debugging Custom Objects
http://msdn.microsoft.com/en-us/library/ms403356.aspx
Developing a User Interface for a Data Flow Component
http://msdn.microsoft.com/en-us/library/ms136029.aspx

Hope this helps. If you have any other questions or concerns, please feel free to let me know. Have a nice day!

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...#notifications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Mike,
Thank you for using Microsoft MSDN Managed Newsgroup. This is Charles. I will assist you on this thread.

Regarding your question, Do I have to do all those things to debug this component?
I think that your question is not a simple debugging scenario. Apparently you are experiencing a process of both re-
deployment and debugging. The debugging step is actually just your step 9. The other steps are for deployment of your
custom component. For the process of deployment, yes, the steps 1-8 are necessary for manual deployment. If you want
to simplify the steps, I think that you may consider creating a command batch file (.bat) to process your steps 1-5. You
may need to write an executable to change the version in your AssemblyVersion attribute and
DtsPipelineComponent.UITypeName, and recompile component. From some .NET experts, I know that you can use some
.NET SDK tools such as vbc.exe and csc.exe to compile an assembly.

The following articles are for developing, deploying and debugging custom objects for SSIS, and from which we can find
that there are indeed many steps required:
Building, Deploying, and Debugging Custom Objects
http://msdn.microsoft.com/en-us/library/ms403356.aspx
Developing a User Interface for a Data Flow Component
http://msdn.microsoft.com/en-us/library/ms136029.aspx

Hope this helps. If you have any other questions or concerns, please feel free to let me know. Have a nice day!

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...#notifications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Mike,
Thank you for using Microsoft MSDN Managed Newsgroup. This is Charles. I will assist you on this thread.

Regarding your question, Do I have to do all those things to debug this component?
I think that your question is not a simple debugging scenario. Apparently you are experiencing a process of both re-
deployment and debugging. The debugging step is actually just your step 9. The other steps are for deployment of your
custom component. For the process of deployment, yes, the steps 1-8 are necessary for manual deployment. If you want
to simplify the steps, I think that you may consider creating a command batch file (.bat) to process your steps 1-5. You
may need to write an executable to change the version in your AssemblyVersion attribute and
DtsPipelineComponent.UITypeName, and recompile component. From some .NET experts, I know that you can use some
.NET SDK tools such as vbc.exe and csc.exe to compile an assembly.

The following articles are for developing, deploying and debugging custom objects for SSIS, and from which we can find
that there are indeed many steps required:
Building, Deploying, and Debugging Custom Objects
http://msdn.microsoft.com/en-us/library/ms403356.aspx
Developing a User Interface for a Data Flow Component
http://msdn.microsoft.com/en-us/library/ms136029.aspx

Hope this helps. If you have any other questions or concerns, please feel free to let me know. Have a nice day!

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...#notifications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Mike,
Thank you for using Microsoft MSDN Managed Newsgroup. This is Charles. I will assist you on this thread.

Regarding your question, Do I have to do all those things to debug this component?
I think that your question is not a simple debugging scenario. Apparently you are experiencing a process of both re-
deployment and debugging. The debugging step is actually just your step 9. The other steps are for deployment of your
custom component. For the process of deployment, yes, the steps 1-8 are necessary for manual deployment. If you want
to simplify the steps, I think that you may consider creating a command batch file (.bat) to process your steps 1-5. You
may need to write an executable to change the version in your AssemblyVersion attribute and
DtsPipelineComponent.UITypeName, and recompile component. From some .NET experts, I know that you can use some
.NET SDK tools such as vbc.exe and csc.exe to compile an assembly.

The following articles are for developing, deploying and debugging custom objects for SSIS, and from which we can find
that there are indeed many steps required:
Building, Deploying, and Debugging Custom Objects
http://msdn.microsoft.com/en-us/library/ms403356.aspx
Developing a User Interface for a Data Flow Component
http://msdn.microsoft.com/en-us/library/ms136029.aspx

Hope this helps. If you have any other questions or concerns, please feel free to let me know. Have a nice day!

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...#notifications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======