Ho we use LibVLCSharp on an Asp.net core razor page ?
I have looked at the LibVLCSharp.NetCore.Sample sample, which is an asp.net core console app
i tried to crate an asp.net core webapplication and try to modify the example to display the video
on the razor page
If what you are asking is to have a VLC based player in the browser, this will be supported when https://code.videolan.org/jbk/vlc.js/ lands.
If what you are asking is use LibVLCSharp on the server to stream to a JS player in a webpage, it is likely possible (though probably not the best tool for the job), but you will have to edit your question with more details as to what you want to know.
The LibVLCSharp.NetCore.Sample is a .net core sample, not an ASP.net core sample.
Displaying a video in a web page is something that goes beyond the usage of libvlc.
See also this issue
Related
I want to create a progressive web app with ASP.NET CORE 2.0 using Razor Pages preferably because I like the code behind architecture of Razor Pages.
Please recommend me a tutorial or docs or any course where I can begin to learn this. I already know ASP.NET CORE so I don't need to learn that, but actually I want to learn and create PWA but at server side I want to use ASP.NET CORE 2.0 and Razor Pages (if possible). And then I will be hosting them in Azure.
The courses I've searched so far on the web, all of them are with node.js or any other server side technology. Which is a problem because I don't want to use JS, except on the front end, where I don't have a choice.
According to your description, I assume that you could refer to the following tutorials for getting started with PWA using .NET Core:
Yeoman PWA Angular 4 & .NET Core
PWA-Asp.NetCore
Building Progressive Web Applications (PWA) with Visual Studio
This is a very common misconception...that the client-side is tightly coupled to the server-side. They are not.
Your ASP.NET application renders pages/html on demand, at run-time, on the server. The site will work with or without the client-side code, that is why it is progressive....
Your PWA/Service Worker code is only concerned with stuff in the browser. You need to think about it as a stateless concern on the client. The service worker can add a proxy layer to the client-side where you can cache and really perform the task ASP.NET or Node Or PHP, etc perform, just in the browser, before the network must be used.
My advice, to learn the concepts, is to create a static version of your site or a test site. Get comfortable with how to make a PWA and a simple caching service worker, then apply it to your ASP.NET site.
There is nothing in ASP.NET itself your service worker needs to know about, well short of your routes. And your routes are independent of ASP.NET.
We should make a decision in our company what architecture to use in new web project. We've already successfully used DevExpress' WPF components and thinking of buying their web products, but don't have enough experience with them. So, the next question is for people who have some experience with DevExpress' web components.
Could we start the solution as standard MVC project built in VS 2013 and then add DevExpress' MVC extensions such as data grid etc. and DevExtreme components (jQuery or AngularJS) as well? If we can do that, could you explain, please, what could be possible difficulties?
I think it isn't a good idea to mix up server-side DevExpress Mvc Extensions and client-side DevExtreme Widgets. If you are comfortable with asp.net mvc and want to use client-side javascript technologies, look at DevExtreme Mvc Wrappers.
It supports a convenient razor syntax to configure widgets. And you can use javascript to handle events, implement client-side templates etc.
To see how it works in action, refer DevExtreme demos.
I searched the web more trying to know what is OWIN (Open Web Interface for .Net). I got more information that it decouples server and application, but I am still confused and I can't understand it well.
Here's a link to a webcast with video and samples on it:
http://brockallen.com/2014/02/28/lidnug-intro-to-owin-and-katana/
I am building an app that consists of a number of plugins. The app and the plugins are built around the service stack framework including the razor engine.
One of the problems I have is that I have to set all of the files to copy always, the final app ends up with a mashup of files from all the plugins. It works but doesn't make it easy to add/remove plugins - ultimately I would like to do this whilst the app is running.
I found razorgenerator which looks like it addresses part of my problem and would precompile the microsoft razor pages into the dll. Has anybody done anything like this with the service stack razor files?
It wasn't really designed for it, but here's an example of using ServiceStack to render stand-alone razor pages.
You could also use another tool like razorgenerator or RazorEngine though this is disconnected and doesn't have anything to do with the Razor support in ServiceStack.
I am new to LWUIT, its indeed a great fun to use it so far. Currently I have to use its browser component to send and receive data to and from the server. Can anybody give me an insight about it or a tutorial so that I can get working into it. Thanks in advance.
If you intend to have browser specific functionality like XML, HTML page rendering in your application than read the following articles
HTML Component Writeup In Ofir's Blog
Mobile web and HTML inside JavaME with LWUIT {Suggested by #Baqueta, Thanks}
Download LWUIT 1.5 and check project 'Browser' under folder 'apps' in lwuit root directory.
.
If you intend to implement communication between client and server using LWUIT than refer LWUIT4IO library packaged with LWUIT 1.5 download. Read the following articles to better understand 'LWUIT4IO' the library.
Introducing LWUIT For IO (LWUIT4IO)
Parsing In LWUIT & LWUIT4IO
Logging & Caching In LWUIT4IO
.
If you intend to communicate with the server from mobile client purely for data exchange then have a look at Generic Connection Framework. Here you can find ample information, sample code snippets and get to know various connection methodologies available for JavaME.