Hi,

as this is now available - where can we find/request the sourcecode?

Best Regards,
Christian

We also have a urgent need for the sourcecode. We want to make a custom view for the scheduler component with custom  functionality. But we do not know if we can add that functionality because the source is not available yet.

Do we really have to wait another 3 months for the source code? Are there possibilities to get parts of the source code?

Dimo, I can see why you would want your customers to regard those two points as "the important information".

For those who don't appreciate ongoing efforts by Progress to distract their customers with such disingenuous messaging, I offer the actual key takeaways for affected developers:

• Progress has invited customers into their ecosystem for years under the pretense that they would always have access to product source code.
• Progress has failed to explain, in concrete terms, their decision to withhold this critical resource for Telerik.Blazor customers (statements like "product, technology, and market considerations" obviously have no meaning).
• While withholding source code from their customers, Progress and their distributors continued to publish misleading marketing materials on the Web, failing to disclose this omission to prospective customers.
• While Progress deprives its customers of this crucial resource, amazing high-quality open-source Blazor component libraries with vibrant communities are appearing every day.
• With each passing day, the mishandling of this situation by Progress, along with the rise of free alternative frameworks for Blazor, will result in a steeper nosedive in renewals by the developers Progress has betrayed.
  

Thanks!

 

@SturmA, you're really expecting a bug fix within 20 days?

It takes them longer than that to post a message to the voting system to determine if other developers feel your bug is important enough for them to even acknowledge.

Many of us have been waiting over a year for Progress to address some of the most egregious defects in this framework.

Again, we need to adjust our expectations. Historically we have dealt with a company called Telerik. That company no longer exists.

https://github.com/telerik/kendo-ui-core/issues/6277

Hello Marin,
hello Maria

you told us how good the telerik supoort is.

Why it takes so long to copy past a small snippet like this into your build system  : 

        /// <summary>
        /// Provides additional view data in the editor template for that event (if any)..
        /// </summary>
        /// <param name="additionalViewData">The AdditionalViewData of the EditorTemplate</param>
        public SchedulerEditableSettingsBuilder<T> AdditionalViewData(object additionalViewData)
        {
            container.AdditionalViewData = additionalViewData;

            return this;
        }

10 lines of code should copy paste into the file SchedulerEditableSettingsBuilder.cs in your source code, i ask me why it takes so long ?
Without access to the source code it's not possible to maintain a project for us.

I opened the ticket at February 5, 2021.

Today i update to 2021.1.224 and really the patch is not included ?

You tell us something about great support and fast support and that we don't need access to the source code because if there is a problem and you open a ticket you get a solution quickly. As in many other cases, I do not see this and I would like to have your opinion. It's a small bug that can be fixed very quickly and I even included the corrected source code in the support ticket the only doing is copy past, so I say the support from Telerik very bad, please prove the opposite to me.

Regards
Arthur

The discomfort that Peter and others are feeling can be explained very simply -- this is not a Telerik product, it is a Progress product. Withholding source code for Telerik.Blazor represents this latest in an increasingly alarming series of abdications of Telerik's traditional role as the "developer-focused" component vendor. Maria's comment, in which she claimed to seek to "provide clarity" and "visibility" obviously provided neither (maybe November, maybe not), a sleight of hand immediately obvious to anyone whose career hinges on these decisions. In private communication with Marin, I have cited multiple examples of Progress failing to disclose omission of Telerik.Blazor source code in their marketing materials and those of their distributors. Despite this, Progress' legal counsel is working under the deranged theory that they're not liable for false advertising claims. It's difficult for me to see a path to redemption for this once-legendary organization.

It's very simple to read the source code with a decompiler anyway, so this delay can only be about admin and/or legal issues. 

If Telerik already supply source for other products then neither of those factors should be an obstacle.

This should be possible to achieve within a week.  Peopplle can then have their own bug fixes until official fixes are released.

There isn't any logical reason I can see that this has to wait until .NET 6 is released on account that Blazor source is changing.  When 6 is released,  it will start changing again.

It has now been almost 13 months since this request was filed. That is bad enough,  but to get an official response after a year saying it will be a total of at least 22 months before anything is done is incredibly bad.

I think the Telerik product for Blazor is fantastic, but the way this part of the business is being run is very shoddy.  I feel sadness and guilt saying that in public,  but it is unfortunately very true :(

Please fix it.

 

Thank you very much Maria, you do a very good job.

Now we have a time frame to plan.

For me the the information that it will be released this year is enough.

But Maria the question from Peter is also very good.

I would have liked to answer them too.

Maybe it has something to do with the fact that the competition does not have access to the source code either?

Blazor source code will always be changing.  Why does this stop Telerik from releasing source code for components already released?

Let's please keep this dialog productive. Marin's objective is to help ensure that we enjoy a positive development experience using Progress tools and frameworks. He is definitely not the one making the decisions on this matter.

Any feelings of betrayal by Progress stemming from this issue should be addressed by your freedom of decision in the component marketplace.

The lack of source code for Telerik.Blazor has been devastating for me. After more than a decade of dedication to this organization, including countless referrals, when I went to reach for the source code, it wasn't there .. and I lost customers as a result. The effect was felt not just by myself, but my family as well. Researching alternative frameworks and rewriting volumes of code in a massive migration effort was the last thing I wanted to deal with during a global pandemic, but I had no choice.

But thinking back, I am grateful for Telerik's past dedication to their other frameworks, in which source code availability gave me a huge advantage. Particularly with UI for WPF, the source allowed me to provide a level of service to my customers that helped me secure a number of important contracts.

Bottom line, do not attack Marin on this issue. If he could provide us with source code, he would. Instead, politely voice your concern, then do what others in our position have done and simply pivot to other frameworks. This is an exciting time for Blazor, and component vendors are doing some amazing things. Check it out, you might be surprised.

Hi Marin,

here my reason why i only migrate to blazor with source code avallable !!!

Your support and documentation is very bad, slow and have a poor quality !!!

So that having the source code can be useful is absolutly wrong, it is absolutely necessary.

The fact that the source code is available for me was clearly the decision to opt for telerik, this more than eliminates the problems with documentation and support. It's fantastic that you can just see what the problem is.
Without this option, we have to look for a better alternative for Blazor and then we will no longer be able to be a customer in the long term.

I have many support tickets with the answer from telerik "It's not a bug its a missing feature !!!"

Actually i can fix such bug/missing features just in time by myself if nessessary and i share the bugfix with telerik but without source code i have a very big problem.

And please don't make a cheap excuse or escape or avoid the bush, tell us only the release date after on year.

I use the Blazor components actually only for the teams client, so no need to migrate to blazor in the next 3 month,
but it would be fair to answer the question after a year.

P.S: Marin you are aware that I triggered the feature request a year ago and you answered James first.
And telerik need over one year for a answer, here you can see the integrity, speed and quality of the telerik support !!!

Regards

Arthur

 

Marin, your concern as to the viability of our respective approaches to maintaining custom builds is appreciated, but distracts from the main point, which is that source code availability has been a cornerstone of the Telerik ecosystem since the beginning of time. It has been your primary differentiator in the component marketplace. Those who rely on access to source code have figured out how to leverage it.

"OSS" has nothing to do with this and should not be part of the conversation. Nobody is suggesting that open source enter into this equation, the concept is completely irrelevant.

Ultimately Marin, the way to understand this is that your customers have customers. So if my customer is demanding that I address a defect in the framework -- or my ability to secure a customer hinges on my ability to address such a defect -- it's not reasonable to have to wait for months or years while other users vote on the importance of the defect to determine if Progress should fix it. Not when we've aligned ourselves with Progress specifically to avoid that scenario. We're here because we depend on source code availability, it really is that simple.

While it's encouraging to finally see a public commitment by Progress to address this painful void (more than a year after the request was logged), I'm sure your customers would like to know the time frame. The inconsistency between Marin's remark ("will be available") and the status of this request ("unplanned") makes this framework a risky choice -- particularly for long-time Telerik customers that have aligned with and supported Progress specifically because paid license holders have always, until now, enjoyed access to product source code. Like SturmA and James Lett, I have been forced to put Telerik.Blazor aside and invest in more viable frameworks that can be patched as needed.

So i understand, that the source code will not available in the past ?

Should we look for an other contract with a open source provider like Avalonia UI Framework or Uno Platform ?

 

It's certainly proving to be very difficult for us to migrate from ASP.NET Core to Blazor as well.  There are some bugs we can't wait to be fixed by Progress Telerik, and in other instances we need to see the source code to understand functionality (where documentation is not clear) to get the desired behavior from the components.  As CTO I may have to now switch our development teams to an alternate provider.

Without the source for us it's not possible to migrate from asp.net core to blazor !!!