.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

Versioning in c#

Posted By:      Posted Date: September 12, 2010    Points: 0   Category :ASP.Net
Hi,  I have a base class which contains 4 methods. Class BaseClass {  Public void A(){} Public void B(){} public void c{} public void d{} }    I have two clients  like ClientA and ClientB. Now I want ,ClientA can access two methods A and D and ClientB can access two methods B and C. How to solve this problem ?. What are the best approach to achieve  this?    

View Complete Post

More Related Resource Links

Foundations: Versioning Workflows


Developers often struggle with versioning workflows and their related classes. Matt Milner discusses the core issues related to workflow versioning and provides recommendations for making changes to workflow definitions, activities, and workflow services.

Matthew Milner

MSDN Magazine May 2009

.NET Zero Deployment: Security and Versioning Models in the Windows Forms Engine Help You Create and


Windows Forms applications solve many of the problems inherent in building Web applications the old fashioned way?with HTML. To demonstrate the use of Windows Forms over the Web, the author takes his existing app, Wahoo!, and ports it to Windows Forms. In doing so, he discusses versioning, linked files, security, storage isolation, the deployment model, and everything else you need to get started building your own Windows Forms apps for the Web.

Chris Sells

MSDN Magazine July 2002

More Versioning Fun With Optional Arguments

In my last blog post , I covered some challenges with versioning methods that differ only by optional parameters. If you haven't read it, go read it. If I do say so myself, it's kind of interesting. ;) In this post, I want to cover another very subtle versioning issue with using optional parameters. At the very end of that last post, I made the following comment. By the way, you can add overloads that have additional required parameters. So in this way, you are in the same boat as before. However, this can lead to subtle bugs. Let's walk through a scenario. Imagine that some class library has the following method in version 1.0. public static void Foo( string s1, string s2, string s3 = "v1" ) { Console.WriteLine( "version 1"...(read more)

Versioning Issues With Optional Arguments

One nice new feature introduced in C# 4 is support for named and optional arguments . While these two features are often discussed together, they really are orthogonal concepts. Let's look at a quick example of these two concepts at work. Suppose we have a class with one method having the following signature. // v1 public static void Redirect( string url, string protocol = "http" ); This hypothetical library contains a single method that takes in two parameters, a required string url and an optional string protocol . The following shows the six possible ways this method can be called. HttpHelpers.Redirect( "http://haacked.com/" ); HttpHelpers.Redirect(url: "http://haacked.com/" ); HttpHelpers.Redirect( "http...(read more)

Web Part Versioning and Deployment (properties only)


Suppose I have a 3<sup>rd</sup> party Web Part (source code provided, with Web Part deployed as a Feature) that’s installed and used in several Sites within a Site Collection.  I want to make changes not to the source code (which would require updating the assembly and deploying the changes as an updated Feature/Solution Package), but to property values of the Web Part that exist.  Say the WP exists on 10 pages, and I want to change the WP’s Title property from “Amazing Vendor Web Part” to “My New Title”.


First, would this be considered an “out-of-band” patch?  Not that it matters terribly how to label this…


Second, would the ideal approach be to simply add code within a Feature Receiver in that Web Parts VS project (the Feat

If you have SharePoint Document Versioning Enabled, do you also use the retention settings?

I am looking for stats on how many environments are out there using document versioning in there libraries but are perhaps not selecting the retention settings. (e.g. "Optionally limit the number of versions to retain" section) This as we all know in SharePoint is a major cause of database growth.
Tony Parker, MSCE . MCTP. MCITP "Anything worth doing, is worth doing right"

Microsoft.mshtml / mshtml.dll versioning and reference issues

Hi, Couldn't find a more relevant section to put this in, so I'll throw it here as I'm coding in C#, although that doesn't really matter. I'm using .NET 4, trying to add a reference to mshtml, and I want to have all the capabilities depending on the version the client has installed. If I add a reference to the COM component called 'Microsoft HTML Object Library', the reference is labelled "MSHTML" and the path points to an assembly in the GAC called 'Microsoft.html' for some reason. Even though I have IE8 installed, it is still missing the IE8 interfaces, which makes me think it is just pointing to the Microsoft.html.dll wrapper instead of generating the reference from the actual COM compoment. The Microsoft.html.dll wrapper is missing the IE8 interfaces, and from what I can tell, this wrapper is somewhat unnecessary with the .NET 4 "Embed Interop Types" feature. The other thing that scares me is the "Specific Version" field on the reference, which is set to true, and I can't change it. What if someone has a lower version of "Microsoft HTML Object Library" than my dev machine? EDIT: Sorry, got a little confused between adding a reference to Microsoft.mshtml .NET assembly and directly to the COM component.  If I add the reference to the COM component, "Specific Version" isn't available in the properties, bu

Document Versioning

Is there a way to customise the version numbers to depict what department they belong to, such as Engineering will be eng1, eng2, eng3 etc and Logistics could be log1, log2, log3 etc?

Subversion and SSIS package versioning ...

I see some posts recommending MS's change control system. We use Subversion and I was wondering if people have any thoughts or ideas on what is the correct way of maintaining SSIS packages in Subversion. Any thoughts or ideas are greatly appreciated.   Thanks  Jagannathan Santhanam

Versioning lists in Sharepoint (not list items)

I need to keep a track of what all changes have been made to a custom list since it was first created. I need to have track of what columns were added/removed and when. I know that we have versioning for list items so as to keep track of what all changes have been made to an item but what I am looking for is versioning of the list itself rather than the list items. Is this possible?

Ribbon not appearing when versioning switched off

Hi, I have a number of publishing sites where the versioning is switched off and does not require check out for pages.  When 'Require Check Out' is true, the ribbon appears as usual (with the Page tab, edit and Browse) and clicking on Edit Page in Site Actions also shows the Page tab of the ribbon.  However, when 'Require Check Out' is false, the ribbon (with the Page and browse tabs, and the edit icon) do not appear.  When clicking on Edit Page in Site Actions, the page does go into edit mode, but the ribbon doesn't appear. Is there a way around this?  If I switch off the publishing feature, editing then saving the page causes a SPListItem error (this appears to be related to having the publishing feature switched off on what was a publishing site).  The end users do not want the complication of versioning or checking in/out. We are using SharePoint 2010 and the web app has been upgraded from SP2007. Thanks Sandra

Assembly versioning best practice question wrt alpha, beta, etc

We'd like to employ some best practices with respect to versioning in our assemblies.  Since I'm coming from a Java+Maven+OSGi background, I'll share its way of doing versioning. Versioning in Java is arbitrary; there are no platform-dictated schemes.  However, for quite some time now, versions have the typical form major.minor.revision[.qualifier] where major & minor are pretty self-explanatory, revision is used to indicate very minor updates like bug fixes/hot fixes, etc, and qualifier is used at the publisher's convenience.  Almost always, the major, minor & revision elements are numeric values, but they don't have to be.  Ordering is as you might expect:  major versions are the most signficant element and are compared by the string's order unless their all numeric, in which case they're compared numerically, then minor, then revision, then qualifier, if present.  So, to give an example of the versioning scheme that a newly created library might go through, consider the following versions with descriptions: 1.0.0.A1 -- alpha 1 1.0.0.A2 -- alpha 2 1.0.0.B1 -- beta 1 1.0.0.M1 -- milestone 1 1.0.0.M2 -- milestone 2 1.0.0.RC1 -- release candidate 1 1.0.0.RC2 -- release candidate 2 1.0.0.RELEASE -- golden release to manufacturing, aka "official" release Notice that the version string for the version considered gol

Assembly versioning strategies

Hi all, I tried once to see what folks are doing about version number strategies, and I guess I was too verbose (see http://social.msdn.microsoft.com/Forums/en/clr/thread/2c3e2bdb-f1ed-4702-af6f-c203e9642378). How to you manage versions in your assemblies?  What's the best practice, especially under source control?  I'd like to convey major.minor.revision, stage (Alpha, Beta, Milestone, Release Candidate, & Release) iteration within stage (Beta 1, Beta 2, RC 1, RC 2) build number (incremental number within stage's iteration) I am well aware that AssemblyVersionAttribute & AssemblyFileVersionAttribute use the convention major.minor.buildNumber.revision, which just doesn't seem to communicate much information to me without some associated cross reference from version to what kind of release it actually is. Your thoughts & opinions are appreciated. Thanks, Matthew PS:  See http://social.msdn.microsoft.com/Forums/en/clr/thread/2c3e2bdb-f1ed-4702-af6f-c203e9642378 for a long version of this question.

Is it possible for list item author to initiate versioning?

Does any one know if there is a way to create versions of list items and have that versioning be initiated by the author of the list item?  By default, if you have versioning turned on for a list, a new version is created anytime the list item is edited, even if that editing is something inconsequential happening, for instance some action in a workflow. This makes for a bevy on inconsequentional versions. What would be great is to provide the user with a button on the editform.aspx page that initiates the versioning.  We have MOSS 2007 and I work in Designer.

How do I move a document library, with versioning, from one website to another.

How do I move a document library, with it's versioning, from one web site to another in MOSS 2007?

Help needed in versioning through code in document library?



I have a situation where i need to move the document form one library(LB1) to another library (LB2) thorugh event handler code. For documents which are not available in LB2 it is working fine but a case where document is already existing in LB2 i need to maintain the version instead , whereas my code is replacing the document already present.

Can anybody help me getting the versioning done through code?


Many Thanks



Automatic Versioning doesn't work


I am working on a class library and the output is obviously a DLL. I specified the version number as 1.0.* so, that everytime I build the project/assembly, the Build-Revision Number combination is changed. I know that the Build Number is set to the number of days since a random, designated start date, and the revision based on the number of seconds since midnight.

But, the Revision Number never gets updated everytime I make a change and build the assembly. It has been the same number 1.0.3919.20360 all the time today no matter how many changes I make to the code and compile the assembly.

I am using VS2010 to develop and build and following is what I have in my AssemblyInfo.vb

<Assembly: AssemblyVersion("1.0.*")> 

'<Assembly: AssemblyFileVersion(    "")> 

I have gone through the following topic and tried the above setting but, it didn't work.


ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend